Nutanix Updated NCP-MCI-6.10 Exam Questions and Answers by arman

Nutanix Protection Policies replicate VM data between clusters using Nutanix’s built-in data protection engine. For inter-site or cloud-based replication, Nutanix documentation specifies that replication traffic can be encrypted using the Data-in-Transit Encryption feature. The internal description states:

“Data-in-Transit Encryption secures replication traffic moving between clusters by encrypting data packets before transmission across external or untrusted networks.”

This is distinct from Data-at-Rest Encryption, which protects stored data on disks but does not secure network traffic. Self-encrypting drives and secure boot only protect the VM locally, not the replication path. Because replication to NC2 travels over the Internet, encryption of the transport channel is mandatory to meet security compliance.

Therefore, the required capability is Data-in-Transit Encryption.

Capacity Runway analytics in Prism Central rely on historical usage data to generate forward-looking projections. Nutanix documentation specifies:

“Capacity runway forecasts require a minimum of 30 days of historical utilization data to build growth rate baselines and trending models.”

The modeling engine uses CPU, memory, and storage trends over time to estimate depletion dates. Insufficient historical data prevents generating meaningful predictions.

Prism Central will display “Not enough data” or simply omit runway metrics until the minimum time window is met.

The 21-day threshold applies to anomaly detection, not runway calculations.

The 3-month and 6-month options refer to optimal historical windows for accuracy but are not required.

Thus, the correct requirement is 30 days of history.

Nutanix performance troubleshooting guidelines emphasize the importance of adequate vCPU resources when diagnosing single-VM performance issues. The documentation states that “under-provisioned CPU is a primary cause of perceived storage latency and throughput limitations, as storage I/O processing and VirtIO-SCSI operations depend heavily on VM compute resources.”

Running a Windows Server VM with only one vCPU significantly constrains its ability to queue and process disk I/O, handle interrupts, and run kernel-level services. This is especially true when multiple disks are attached. Adding a second controller does not solve underlying CPU bottlenecks. Adjusting br0 TCP settings is not applicable to storage. Increasing CVM resources is unnecessary because the problem is isolated to a single VM while the cluster and other VMs perform normally.

Therefore, increasing vCPU allocation is the required corrective action.

Agent VMs, such as CVMs (Controller VMs) or Witness VMs, have strict affinity and anti-affinity rules to ensure they remain on specific hosts and maintain data consistency and high availability. If an agent VM is powered off and then manually started on another host, it becomes unresponsive because it breaks these rules.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“Agent VMs have specific configuration and affinity constraints. Manually starting them on another host violates these constraints, resulting in the agent VM becoming unresponsive to the cluster.”

Further clarification:

“The cluster expects the agent VM to be on a particular host. Moving it manually to another host breaks this expectation and causes the VM to be unable to properly join the cluster services, leading to an unresponsive state.”

Therefore, it is essential to avoid manually starting agent VMs on different hosts, as doing so can disrupt cluster services.