Nutanix Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI v6.10) NCP-MCI-6.10 Exam Dumps: Updated Questions & Answers (December 2025)

The Nutanix ECA course addresses data protection mechanisms, including how to safeguard disaster recovery (DR) snapshots from inadvertent or malicious deletion. Ensuring that DR snapshots are protected while providing notification requires a policy-based approach to control and monitor deletion actions. The ECA course emphasizes the use ofApproval Policiesin Prism Central to enforce oversight on critical operations like snapshot deletion.

Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:

Module: Data Protection, Section: Approval Policies"Approval Policies in Prism Central allow administrators to enforce review and approval for operations such as snapshot deletion. By creating an Approval Policy for DR snapshots, administrators can ensure that deletion requests are reviewed by designated approvers, preventing unauthorized or accidental deletions and providing notifications to relevant stakeholders."

Module: Prism Central Management, Section: Policy Engine"To protect critical resources like DR snapshots, an Approval Policy can be applied to require approval for deletion actions. This ensures that no snapshot is deleted without explicit authorization, and notifications are sent to approvers to maintain oversight."

Explanation of Options:

A. Create and Apply an Approval PolicyThis is the correct answer. An Approval Policy in Prism Central is the best way to protect DR snapshots from inadvertent or malicious deletion. The policy requires designated approvers to review and authorize snapshot deletion requests, ensuring oversight and preventing unauthorized actions. Notifications are sent to approvers, meeting the requirement for awareness of deletion attempts. The ECA course highlights:"Approval Policies are ideal for protecting critical data assets, such as DR snapshots, by enforcing a mandatory review process before deletion."

B. Create and Apply an Alert PolicyThis is incorrect. Alert Policies in Nutanix are used to notify administrators of system events or thresholds (e.g., high CPU usage or disk failures) but do not prevent actions like snapshot deletion. While an Alert Policy could notify administrators after a deletion occurs, it does not provide proactive protection or require approval, failing to meet the question’s requirements. The ECA course states:"Alert Policies are reactive and designed to notify administrators of events, not to control or prevent actions like snapshot deletion."

C. Assign DR Admin Role to usersThis is incorrect. Assigning a DR Admin Role grants users permissions to manage DR operations, including snapshot deletion, but does not add protection or notification mechanisms. In fact, it could increase the risk of deletion by granting more users access. The ECA course notes:"The DR Admin Role provides administrative privileges for data protection tasks but does not enforce approval workflows or protect against unauthorized deletions."

D. Create a Playbook to alert on eventThis is incorrect. Playbooks in Nutanix Flow or Prism Central are used to automate responses to events (e.g., scaling resources or sending alerts), but they are not designed to prevent snapshot deletion or enforce approval workflows. A Playbook could alert administrators after a deletion event, but it lacks the proactive control provided by an Approval Policy. The ECA course clarifies:"Playbooks are suited for automated remediation or notifications but cannot enforce approval for actions like snapshot deletion."

Additional Context from ECA:

Approval Policy Workflow: In Prism Central, an Approval Policy can be created underPolicies > Approval Policies, specifying DR snapshots as the target resource and defining approvers. When a user attempts to delete a protected snapshot, the request is queued for approval, and notifications are sent to approvers via email or Prism Central’s interface.

Use Case: For DR snapshots, which are critical for recovery, Approval Policies ensure that only authorized personnel can approve deletions, reducing the risk of data loss.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) supports the ECA documentation: "Approval Policies in Prism Central provide granular control over operations like snapshot deletion, ensuring critical DR resources are protected through mandatory approval workflows."

Moving vDisks to a storage container with compression enabled ensures better data efficiency without downtime.

Option A (Migrate vDisks) is correct:

vDisk migration is non-disruptiveand allows compression settings to be applied dynamically.

Option B (Recreate the VM) is incorrect:

Rebuilding the VM is unnecessaryand would causedowntime.

Option C (Migrate the VM) is incorrect:

VM migration does not guarantee that only vDisks move, and it may disrupt performance.

Option D (Recreate vDisk) is incorrect:

This method ismanual and time-consuming, while Nutanix provides anautomated approach.

When synchronous replication fails immediately between two clusters, it is often due to blocked communication across the required ports (2009 and 2020). These must be open manually if the clusters are in different subnets or if network policies block traffic.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“Replication communication relies on specific ports, which must be allowed through the firewall. If the clusters are in different subnets or if there are external firewalls, these ports must be explicitly opened.”

“The modify_firewall command is used to open or close ports on cluster nodes. For replication and remote site communication, eth1 is typically used for external replication traffic.”

Since eth1 is typically used for external connectivity and replication traffic, opening ports on this interface using modify_firewall resolves the communication block.

The Nutanix AHV virtualization guide explains that vGPU-enabled VMs can be live migrated only when the destination host contains compatible GPU hardware and has available vGPU capacity matching the profile assigned to the VM. The documentation states that the VM must have "adequate and equivalent GPU resources on the target host" for migration to proceed. Host affinity is a limiting factor and not a requirement. Agent VMs are not designed to be migrated. Changing the vGPU profile is not necessary as long as the target host supports the currently assigned profile. Therefore, ensuring the destination host has sufficient compatible resources is the required condition.

Application discovery in Prism Central requires sufficient Prism Central resources and an active internet connection to retrieve application signatures.

Option A (Sufficient Prism Central VM resources) is correct:

Prism Central needsadequate CPU and memoryto process application signatures and discovery data.

Option B (Internet connection) is correct:

Application discovery depends on Nutanix’scloud databaseto recognize application patterns.

Option C (API key and key ID) is incorrect:

API keys are not requiredfor automatic application discovery.

Option D (Network controller enabled) is incorrect:

Application discoverydoes not depend on a network controller feature.

Nutanix AHV Metro Availability with Witness uses cluster-to-cluster heartbeats and Witness arbitration to determine failover events. Internal design notes state:

“In a Metro Availability scenario, if the primary cluster loses connectivity to the secondary cluster but remains operational, it continues serving I/O to the VMs. No automatic failover occurs unless the cluster is determined to be down.”

Also:

“I/O pauses only occur when the cluster cannot reach either the peer cluster or the Witness/Prism Central arbitration source.”

Applying this to the scenario:

Both metro clusters lose connectivity with each other.

The primary cluster also loses connectivity to Prism Central.

The recovery cluster remains connected to Prism Central.

Since the primary cluster cannot reach the recovery cluster nor Prism Central, the arbitration path is lost. This triggers the “I/O stall for safety” condition described as:

“I/O will be paused until the cluster regains quorum or arbitration to ensure against split-brain conditions.”

But because the primary clusteris still runningand is not declared failed (just isolated), VMs continue running and I/O is paused only as long as arbitration is unreachable.

Thus:

Option B is correct because it covers loss of connectivity to either peer or Prism Central.

Option C is correct because VMs do continue running; only I/O is paused to prevent inconsistency.

Automatic failover only happens when Witness declares the primary unreachable by quorum rules, which is not the case here since only one side can see the Witness.

Nutanix storage container configuration guidance specifies that “Advertised Capacity” is the setting used to define a maximum limit for the container. This value enforces a hard cap on space usage. Reserved Capacity, in contrast, defines a minimum guarantee of space for the container and does not limit growth.

Prism Element is the correct interface for creating storage containers with specific data reduction settings such as compression and deduplication, as the container-level storage policies are applied directly at the cluster’s storage layer.

The documentation further clarifies that RF1, inline compression, and deduplication settings are configured within Prism Element under container creation. Therefore, to enforce the 100 GiB limit, the administrator must create the container in Prism Element and set the Advertised Capacity to 100 GiB.

Within Nutanix Recovery Plans, IP address transformations are handled through an automated mechanism known asIP Address Mapping. The documentation describes two methods: fixed mappings and offset-based mappings.

Offset-based mapping allows administrators to maintain consistent host identity attributes such as the last octet while shifting only the subnet portion during DR failover. The internal guidance states, “Offset-based mapping enables automatic recalculation of target IP addresses using offsets applied to source subnets, allowing preservation of host-specific octets across networks.”

Custom scripts are possible but not recommended because Nutanix already provides a built-in, automated IP transformation system. Editing IPs inside VMs after failover is operationally expensive and defeats the purpose of an orchestrated DR workflow. IPAM is useful for dynamic IP assignment but does not preserve the last octet mapping requirement.

Thus, Offset-based IP mapping is the correct mechanism for this requirement.