Syslog severity levels follow a standard numerical system, where lower numbers indicate higher

severity.

Option B (Severity Level 2) is correct:

Level 2 = CRITICAL → Used for serious conditions requiring immediate attention.

Audit logs often generate Critical logs related to security, access violations, or major failures.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/Nutanix_NCP-MCI-6.10/page_55_img_1.jpg

Options A (0), C (5), and D (7) are incorrect:

0 = Emergency (Too severe, only used for full system failures).

5 = Notice (Not critical, used for general system events).

7 = Debug (Not relevant for critical logs).

Nutanix Security Guide → Syslog Integration and Severity Levels

Nutanix KB → Configuring Syslog for Prism Central Audit Logs

For workloads requiring new IP addresses and DNS server settings during DR recovery, using custom

scripting within the Recovery Plan is the recommended and supported method.

From the Nutanix Enterprise Cloud Administration (ECA) course materials:

“Recovery Plans support scripting within the Recovery Sequence to enable administrators to perform

post-recovery customization tasks, such as updating IP addresses, configuring DNS, or applying

application-specific settings.”

“This scripting capability provides a flexible, automated approach to ensure that VMs are correctly

reconfigured to operate within the DR environment’s network and DNS settings.”

This avoids the need for manual reconfiguration post-recovery or adjusting settings in production

prior to failover.

Thank you for your visit.

Understanding the Issue

The administrator is investigating VM performance complaints and is analyzing CPU Ready Time

data.

CPU Ready Time is a crucial metric in Nutanix and virtualization environments (AHV, ESXi, or Hyper-

V).

It measures the amount of time a VM is waiting for CPU scheduling due to resource contention.

High CPU Ready Time indicates that VMs are ready to run but are waiting because the host lacks

available CPU resources.

Analysis of the Exhibit

The graph shows CPU Ready Time spikes for multiple VMs.

Some VMs have CPU Ready Time exceeding 18% to 21.5%, which is very high.

A healthy CPU Ready Time should be below 5%.

Values above 10% indicate CPU contention, and anything above 20% is critical and requires

immediate troubleshooting.

Evaluating the Answer Choices

❌ (A) Check the number of vCPUs assigned to each CVM. (Incorrect)

CVMs (Controller VMs) have fixed CPU allocation, and modifying their vCPU count is not

recommended unless advised by Nutanix Support.

The issue is related to VM CPU contention, not CVM configuration.

✅ (B) Review host CPU utilization. (Correct Answer)

High CPU Ready Time suggests CPU overcommitment or host saturation.

The administrator should check host CPU usage in Prism Central to determine if the cluster is

overloaded.

If host CPU usage is consistently above 85–90%, VMs are competing for CPU resources, leading to

high CPU Ready Time.

❌ (C) Assess cluster SSD capacity. (Incorrect)

SSD capacity impacts storage performance (latency, read/write speeds) but does not affect CPU

Ready Time.

High CPU Ready Time is a CPU scheduling issue, not a storage bottleneck.

❌ (D) Enable VM memory oversubscription. (Incorrect)

Memory oversubscription does not impact CPU scheduling.

Enabling memory oversubscription affects RAM allocation, but CPU Ready Time is strictly related to

CPU contention.

Next Steps to Diagnose & Resolve the Issue

Review Host CPU Utilization:

Navigate to Prism Central → Analysis → CPU Usage per Host.

Identify hosts experiencing high CPU load.

Check VM vCPU Allocation:

Ensure that VMs do not have excessive vCPUs assigned, which can lead to scheduling inefficiencies.

Overprovisioning vCPUs can cause unnecessary contention.

Balance Workload Across Hosts:

Use Nutanix AHV DRS (Dynamic Scheduling) or VMware DRS to redistribute VMs across hosts.

Check if certain hosts are overloaded while others have spare CPU capacity.

Consider Scaling Out the Cluster:

If CPU usage is consistently high, adding more nodes may be required to reduce CPU contention.

Multicloud Infrastructure

& Best Practices

CPU Ready Time Best Practices:

Keep CPU Ready Time below 5%.

Avoid overcommitting vCPUs on heavily loaded hosts.

Monitor Prism Central Runway Metrics to predict future CPU resource needs.

Nutanix AHV CPU Scheduling Optimization:

Ensure proper VM sizing (avoid excessive vCPU allocation).

Balance workloads using Nutanix AHV DRS.

References:

Nutanix Prism Central: Performance Analysis and CPU Metrics

Nutanix Bible: VM Performance and Resource Management

Nutanix KB: Troubleshooting High CPU Ready Time in AHV

To ensure VM high availability (HA) in the event of a node failure, the administrator must enable HA

Reservation (Option B) in Prism Element.

High Availability (HA) in Nutanix ensures that VMs restart on another available node if the host they

are running on fails.

Option A (Redundancy Factor 3) affects storage redundancy, not VM failover.

Option C (Protection Domains) is related to disaster recovery (DR), not local HA failover.

Option D (RF1 Storage Container) would reduce fault tolerance and is not recommended for

production environments.

Nutanix Prism Element Guide → Configuring HA Reservation

Nutanix Bible → High Availability (HA) and Failover

Nutanix Support KB → VM Recovery with HA Enabled

For optimal Disaster Recovery performance, new nodes must match or exceed the storage

performance of existing nodes.

Option A (New node must have at least 2 SSDs) is correct:

Since the G7 nodes have two SSDs, replacing G5 nodes with at least 2 SSDs ensures consistent SSD

cache and performance.

Option B is incorrect:

G7 or G8 nodes may help, but storage performance is more critical for DR.

Option C is incorrect:

CPU core count does not impact DR storage performance as much as SSD capacity.

Option D is incorrect:

Hybrid nodes are already in use, but SSDs must match for performance balance.

Nutanix Hardware Guide → Choosing Nodes for Hybrid and DR Clusters

Nutanix KB → Balancing Storage Across Different Hardware Generations

Active-Active bonding allows multiple network interfaces to be used simultaneously, improving

bandwidth and redundancy.

Option B (Active-Active) is correct:

This mode enables load balancing across all available adapters, providing higher throughput and fault

tolerance.

Option A (No Uplink Bond) is incorrect:

Without a bond, VMs cannot benefit from multiple adapters.

Option C (Active-Active with MAC pinning) is incorrect:

MAC pinning binds traffic to a single NIC, limiting bandwidth distribution.

Option D (Active-Backup) is incorrect:

This mode only provides failover, not increased bandwidth.

Nutanix AHV Networking Guide → Bonding Modes and Load Balancing

Nutanix KB → Optimizing Network Throughput in AHV

https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Security-Guide-v6_10:mulconfigure-data-in-transit-encryption-pc-t.html

"Ensure that port 2009 is open between the Prism Central instances for the KMS cluster to

communicate."

This is explicitly stated in the "Firewall rules for Data-in-Transit Encryption" section for Prism Central.

Technical Context:

Port 2009 is used by ZooKeeper (the coordination service for the KMS cluster) in Scale-Out Prism

Central deployments.

DiTE in Prism Central relies on a dedicated KMS cluster that synchronizes encryption keys across PC

instances using this port.

Firewall blocks on port 2009 break KMS quorum, preventing key exchange and causing DiTE to fail.

In Nutanix Prism Central, user-generated reports in Intelligent Operations are stored for a limited

time and then deleted automatically.

Option C (Reports are automatically deleted after 24 hours) is correct:

Reports do not persist indefinitely unless they are scheduled reports.

One-time reports expire after 24 hours.

Option A (Cluster Viewer deleted the report) is incorrect:

Cluster Viewer does not have permissions to delete reports.

Option B (Report was archived) is incorrect:

Nutanix does not automatically archive reports.

Option D (Report stored in Prism Element) is incorrect:

Reports are generated and stored only in Prism Central, not Prism Element.

Nutanix Prism Central Guide → Intelligent Operations & Report Retention Policies

Nutanix KB → Why Reports in Prism Central Are Not Persisting

:

: