Pass the Nutanix NCM-MCI NCP-MCI-6.10 Questions and answers with Dumpstech

High SSD utilization in a hybrid cluster can lead to increased I/O latency as new writes may spill over to HDDs, reducing overall performance.

Option D (Average I/O latency in the cluster may increase) is correct:

If SSD usage isabove 75%,data tiering shifts to slower HDDs,increasing latency.

Option A is incorrect:

SSD failures are managed via redundancy policies (RF2/RF3), and high utilizationdoes not impact failure handling.

Option B is incorrect:

Metadata is stored separately, and high SSD usage does not mean metadata is at risk.

Option C is incorrect:

Clusters do not go into read-only mode due to high SSD utilization—they simply experienceperformance degradation.

Data-in-Transit Encryption for Prism Central and CVMs requires specific internal communication ports to be open. Nutanix internal component documentation states:

“Port 2020 is used by the Nutanix encryption service for encrypted CVM-to-CVM communication during Data-in-Transit Encryption operations.”

This port is essential for establishing secure tunnels between control-plane services. Ports 2009 and 2010 are used by other CVM services (e.g., Stargate, Curator coordination) but not for transport encryption. Port 9440 is for Prism UI/API traffic, and while it must be accessible for management, it does not enable encrypted back-end service traffic.

Thus, the administrator must ensure that port 2020 is permitted to enable Data-in-Transit Encryption functionality.

To resolve issues with application-consistent snapshots (script execution failures), two critical actions are needed:

NGT Service Status:From the ECA materials:

“The Nutanix Guest Tools (NGT) service is responsible for executing pre-freeze and post-thaw scripts for application-consistent snapshots. If NGT is not running, these scripts will not execute.”

Script Validation:

“Before relying on scheduled snapshot runs, execute pre-freeze and post-thaw scripts manually to ensure they complete successfully. This helps to rule out script logic or permission issues.”

Ownership or log review of the script path itself (A and B) are secondary and typically not root-cause resolution steps.

The best way to test the performance of a Linux VM that is underperforming at the storage level on an ESXi cluster, while minimizing downtime, is to migrate the VM to an AHV-based cluster. This allows leveraging Nutanix-native storage optimizations and hypervisor capabilities of AHV.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“AHV and Nutanix storage integration is natively optimized for performance, leveraging capabilities like data locality, I/O path enhancements, and advanced metadata management. Migrating workloads from ESXi to AHV can often resolve performance bottlenecks associated with storage I/O.”

Additionally:

“Using the Nutanix Move tool, administrators can migrate running VMs between different hypervisors (e.g., ESXi to AHV) with minimal downtime and fully automated steps, reducing the operational burden.”

Increasing vCPUs would not address storage-level performance issues, and collapsing disks would require significant reconfiguration and VM downtime. vDisk sharding is not directly user-configurable and not applicable in this scenario.

Within Nutanix VM classification, Agent VMs are special-purpose system VMs designated for infrastructure tasks. The internal definition states:

“Agent VMs are not live-migratable and do not participate in high-availability evacuation; they are excluded from standard host maintenance operations.”

If a VM is mistakenly marked as an Agent VM, the hypervisor will block all migration attempts. Disabling the Agent VM flag returns the VM to standard workload treatment, making it eligible for live migration.

Updating LLDP has no relevance to VM migration. Backplane port groups affect CVM networking only. ADS influences workload placement but not migration eligibility.

Therefore, removing the Agent VM designation is required to allow migration.

Dead VMs and Zombie VMs are different classifications of inactive VMs in Nutanix, and their deletion timelines depend on Playbook configuration.

Dead VMs→ Consideredinactive after 30 days, then must wait99 more daysbefore deletion.

Total time: 30 + 99 = 129 days.

(Option C is correct).

Zombie VMs→ Consideredinactive after 30 days, then must wait99 more daysbefore deletion.

Total time: 30 + 99 = 129 days.

(Option B is correct).

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.

Scale-out Prism Central deployments consist of multiple nodes running the Prism Central service. Nutanix documentation emphasizes that:

“When deploying multi-node Prism Central, an FQDN backed by DNS can provide request distribution across all Prism Central nodes, enabling load balancing and increased concurrency.”

A Virtual IP in contrast only directs traffic to a single active Prism Central node. Internal behavior notes:

“A VIP is not active-active; it designates one node as primary for all inbound requests.”

“Using an FQDN with DNS round-robin or an external load balancer allows the cluster to distribute workload across all PC nodes.”

The FQDN allows:

distributing API/UI traffic across multiple Prism Central nodes

improving performance under heavy load

enabling parallel query handling

avoiding bottlenecks on the primary node

SSL certificates apply to either VIP or FQDN. Segmentation and resiliency are unrelated to FQDN usage.

Thus, the correct answer is Load Balancing.

Snapshots that are part of an active recovery operation cannot be deleted until the process is completed or manually canceled.

Option A (Active recovery in progress) is correct:

Nutanix does not allow deletion of snapshots ifthey are being used in an ongoing recovery process.

The administrator shouldverify whether the snapshot is currently part of a Protection Domain or Disaster Recovery (DR) plan.

Option B (Ransomware encryption) is incorrect:

Nutanix snapshots are immutable by defaultandcannot be encrypted by external threats.

Option C (Approval policy denial) is incorrect:

Snapshot deletionsdo not require manual approval, unless controlled by an external workflow system.

Option D (Snapshot corruption) is incorrect:

Nutanixuses checksums to prevent corruption, so snapshots cannot besilently damaged.