Curious about Actual Nutanix Certified Professional (NCP-MCI-6.10) Exam Questions?

Correct : C

Metro Availability requires that VMs always read data from their primary site to maintain optimal performance and prevent remote data access latency.

Option C (Migrate the VM to its primary site and set appropriate rules) is correct:

If a VM fails over to the secondary site but is still running in the primary site, it will read data remotely, causing high latency and performance issues.

The solution is to migrate the VM back to the primary site and configure DRS rules or host affinity settings to prevent unwanted movement.

Option A is incorrect:

The command lists active Metro Availability protection domains but does not resolve the issue.

Option B is incorrect:

Must-affinity rules can help, but they should be configured after migrating the VM back to the primary site.

Option D is incorrect:

Running NCC health checks will only diagnose the issue, not resolve it.

Nutanix Bible Metro Availability and Data Locality

Nutanix Best Practices VM Affinity Rules for Metro Availability

Nutanix KB Troubleshooting Remote Data Access in Metro Availability

Correct : A

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 if they are being used in an ongoing recovery process.

The administrator should verify 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 default and cannot be encrypted by external threats.

Option C (Approval policy denial) is incorrect:

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

Option D (Snapshot corruption) is incorrect:

Nutanix uses checksums to prevent corruption, so snapshots cannot be silently damaged.

Nutanix Protection Policies Snapshot Retention and Deletion

Nutanix Bible Backup & Disaster Recovery Mechanisms

Nutanix KB How to Delete a Snapshot Used in Recovery Plans

Correct : D

Nutanix uses IPv4 multicast for automatic node discovery and cluster expansion.

Option D (IPv4 multicast must be allowed) is correct:

When adding new nodes, the Nutanix Cluster automatically detects them using IPv4 multicast traffic.

If multicast is blocked at the switch level, the new nodes will not be discovered automatically.

Option A (Hypervisor version must match) is incorrect:

While the hypervisor version should be compatible, it does not impact node discovery.

Option B (IPv6 multicast) is incorrect:

Nutanix does not use IPv6 multicast for cluster discovery.

Option C (AOS version must match) is incorrect:

Nodes can have slightly different AOS versions, but discovery still works as long as they are compatible.

Nutanix Best Practices Cluster Expansion & Auto-Discovery

Nutanix KB Why Nutanix Requires IPv4 Multicast for Node Discovery

Correct : A

In a scale-out Prism Central deployment, using an FQDN (Fully Qualified Domain Name) enables load balancing across multiple Prism Central instances.

Option A (Load balancing) is correct:

When an FQDN is used, Nutanix automatically distributes traffic between multiple Prism Central nodes, improving performance.

Option B (Resiliency) is incorrect:

Resiliency is achieved through cluster redundancy, not by using an FQDN.

Option C (Segmentation) is incorrect:

Segmentation relates to network isolation rather than FQDN-based load balancing.

Option D (SSL Certificate) is incorrect:

SSL certificates can be applied to both FQDN and Virtual IP configurations.

Nutanix Prism Central Guide Configuring Scale-Out Deployment

Nutanix KB How FQDN Enhances Load Balancing in Scale-Out Prism Central

Correct : C

Enabling 'Cluster Lockdown' in Nutanix is the best security measure to prevent password-based SSH logins.

Option C (Enable Cluster Lockdown) is correct:

Cluster Lockdown disables password-based SSH and requires key-based authentication.

Option A (Rename the nutanix user) is incorrect:

The Nutanix user is a system account and cannot be renamed.

Option B (Block port 22) is incorrect:

This would prevent all SSH connections, including key-based logins, making administration difficult.

Option D (Delete the nutanix user) is incorrect:

The nutanix user is required for system operations and cannot be removed.

Nutanix Security Guide Implementing Cluster Lockdown

Nutanix KB Best Practices for SSH Security on CVMs