Quiz NCP-MCI: Nutanix Certified Professional - Multicloud Infrastructure v6.5

The exhibit shows that the overall runway is only 66 days, meaning that the current cluster does not
have enough capacity to sustain workloads for 6 months, let alone 9 months.
The best solution is to add resources to the cluster (Option A), such as CPU, memory, or storage, to
extend the runway.
Postponing new workloads (Option B) may help in the short term but does not align with the
business need to continue adding workloads.
Deleting workloads (Option C) is not a viable option because the customer wants to add more, not
remove them.
Changing the target to 9 months (Option D) does not change the actual resource constraints; it only
alters the target timeframe.
Reference:
Nutanix Prism Central → Capacity Planning and Runway Analysis
Nutanix Bible → Cluster Resource Management and Scaling
Nutanix Support KB → How to Extend Cluster Runway with Resource Scaling

For Metro Availability to work properly, the storage containers at both the primary and secondary
sites must meet certain requirements:
The storage containers must have the same name (Option D). This ensures that replication and
failover work seamlessly. If the names do not match, the storage containers will not be listed as
compatible.
The destination storage container must be empty (Option C). Metro Availability requires a clean
storage container at the secondary site to receive data. If the container already contains data, it
cannot be used.
Option A is incorrect: Different vendor hardware does not affect Metro Availability compatibility.
Option B is incorrect: Compression does not affect Metro Availability compatibility. However, it is
recommended to keep compression settings aligned between sites.
Reference:
Nutanix Documentation: Metro Availability Deployment Guide
Nutanix Best Practices for Metro Availability
Nutanix KB 2093: Troubleshooting Metro Availability Storage Container Issues

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 Reference & 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.
Reference:
Nutanix Prism Central: Performance Analysis and CPU Metrics
Nutanix Bible: VM Performance and Resource Management
Nutanix KB: Troubleshooting High CPU Ready Time in AHV

When using FQDN instead of a Virtual IP in a scale-out Prism Central deployment, Nutanix enables
load balancing across multiple Prism Central instances.
Option A (Load balancing) is correct because it ensures that requests are distributed among multiple
Prism Central nodes, improving performance and redundancy.
Option B (Resiliency) is incorrect because resiliency is achieved through HA and replication, not
through FQDN configuration.
Option C (Segmentation) is incorrect because network segmentation is handled at the VLAN or
security policy level.
Option D (SSL Certificate) is incorrect because SSL certificates can be applied regardless of whether
FQDN or Virtual IP is used.
Reference:
Nutanix Prism Central Deployment Guide
Nutanix Best Practices for Scale-Out Prism Central
Nutanix Support KB: Configuring FQDN for Prism Central

In Nutanix Capacity Planning, Overall Runway represents how long the cluster can support current
and new workloads before resources are exhausted.
Even if the runway is below 365 days, the system considers the cluster to be in good shape if new
workloads are sustainable (Option B).
Option A is incorrect: Storage runway alone is not the only factor; CPU and memory are equally
important.
Option C is incorrect: The presence of recommended resources does not mean the cluster is in good
shape.
Option D is incorrect: The target of 1 month affects projections but does not explain why the cluster
is in good shape.
Reference:
Nutanix Prism Central → Capacity Runway and Planning
Nutanix Bible → Workload Placement and Cluster Sizing
Nutanix Support KB → Capacity Planning Best Practices

For Nutanix Disaster Recovery (DR) protection policies, the first step is to establish a connection
between the Production cluster and the DR site, which is done by creating an Availability Zone (AZ)
(Option B).
Availability Zones (AZs) define remote sites for replication and are a requirement for configuring
protection domains and disaster recovery plans.
Option A (Installing NGT) is not necessary for setting up replication but is useful for application-
consistent snapshots.
Option C (Converting the source cluster to AHV) is not required, as Nutanix supports cross-hypervisor
DR between ESXi and AHV.
Option D (Creating a point-in-time snapshot) is a later step after setting up the Availability Zone and
Protection Policy.
Reference:
Nutanix Protection Policies and DR Documentation
Nutanix Bible → Disaster Recovery Planning
Nutanix Support KB → Configuring Availability Zones in Prism Central

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.
Reference:
Nutanix Prism Element Guide → Configuring HA Reservation
Nutanix Bible → High Availability (HA) and Failover
Nutanix Support KB → VM Recovery with HA Enabled

When performing a Life Cycle Manager (LCM) upgrade, the recommended way to stop the process is
to use the “Stop Update” feature in LCM (Option D).
Option A (Cancel via Ergon ecli) is not a recommended approach since manually interfering with
running tasks can cause inconsistencies.
Option B (lcm_task_cleanup.py script) is used for post-upgrade cleanup but does not stop ongoing
updates.
Option C (Restarting Genesis) does not stop an LCM upgrade and can cause instability.
Reference:
Nutanix Life Cycle Manager (LCM) User Guide
Nutanix KB: Best Practices for Stopping and Restarting LCM Tasks
Nutanix Prism Central → LCM Feature Documentation

The most efficient way to allow team leads to manage a specific set of VMs is by creating a Project
(Option C) in Prism Central and assigning the team leads to that Project.
Nutanix Projects allow administrators to control VM access based on groups and permissions,
ensuring that users only manage VMs assigned to their project.
Option A (Role Mapping) applies more broadly to roles but does not restrict access to specific VM
groups.
Option B (VPC Admin) is related to network segmentation, not VM access control.
Option D (Security Policies) are used for network and firewall rules, not VM access control.
Reference:
Nutanix Prism Central → Projects and Role-Based Access Control (RBAC)
Nutanix Bible → Multi-Tenancy and Project-Based Access Control
Nutanix KB → Setting Up Role-Based Access Control (RBAC) for Prism Central

Nutanix requires that all cluster components synchronize time using an external NTP (Network Time
Protocol) server.
Option A (Adding an external NTP server) is correct because Nutanix best practices recommend using
an external time source to prevent clock drift between cluster nodes.
Option B (DNS server IP) is incorrect: A DNS server does not provide NTP services.
Option C (Server with DNS hostname) is incorrect unless the DNS hostname resolves to an NTP
server.
Option D (IP of the Domain Controller) is incorrect because not all domain controllers provide NTP
services unless explicitly configured.
Reference:
Nutanix Best Practices: NTP Configuration for Hyper-V Clusters
Nutanix KB: Ensuring Proper Time Synchronization Across Cluster Nodes
Nutanix Documentation: Prism Central NTP Settings Configuration