Nutanix NCP-MCI-6.10 Practice Exams
Last updated on Oct 07,2026- Exam Code: NCP-MCI-6.10
- Exam Name: Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI v6.10)
- Certification Provider: Nutanix
- Latest update: Oct 07,2026
Question #51
An administrator wants to ensure that VMs can be migrated and restarted on another node in the event of a single-host failure.
What action should be taken in Prism Element to meet this requirement?
- A . Set Redundancy Factor to 3.
- B . Enable HA Reservation.
- C . Configure a Protection Domain.
- D . Configure an RF1 storage container.
Correct Answer: B
B
Explanation:
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
B
Explanation:
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
Question #52
An administrator needs to set up a protection policy in preparation for a Disaster Recovery (DR) test.
What is the first step required to satisfy this task?
- A . Install NGT (Nutanix Guest Tools) on VMs where applications are supported.
- B . Create an Availability Zone between Production and DR.
- C . Convert the source cluster to AHV.
- D . Create a point-in-time snapshot of source VMs.
Correct Answer: B
B
Explanation:
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
B
Explanation:
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
Question #53
What feature allows receiving a weekly message about infrastructure performance summary?
- A . Admin Center Life Cycle Manager
- B . Prism Central Syslog
- C . Infrastructure VMs List
- D . Intelligent Operations Reports
Correct Answer: D
D
Explanation:
Nutanix Intelligent Operations Reports (Option D) provide weekly summaries of cluster health, performance, and resource consumption.
These reports include recommendations for optimization, alerts, and forecasted resource usage trends.
Option A (Admin Center LCM) manages firmware and software upgrades but does not generate weekly performance reports.
Option B (Prism Central Syslog) is used for logging and event tracking, not performance summaries.
Option C (Infrastructure VMs List) provides a static list of VMs but does not generate periodic reports.
Reference: Nutanix Prism Central → Intelligent Operations and Reports Nutanix Bible → Automated Insights for Cluster Health Monitoring Nutanix KB → Using Intelligent Operations Reports for Capacity Planning
D
Explanation:
Nutanix Intelligent Operations Reports (Option D) provide weekly summaries of cluster health, performance, and resource consumption.
These reports include recommendations for optimization, alerts, and forecasted resource usage trends.
Option A (Admin Center LCM) manages firmware and software upgrades but does not generate weekly performance reports.
Option B (Prism Central Syslog) is used for logging and event tracking, not performance summaries.
Option C (Infrastructure VMs List) provides a static list of VMs but does not generate periodic reports.
Reference: Nutanix Prism Central → Intelligent Operations and Reports Nutanix Bible → Automated Insights for Cluster Health Monitoring Nutanix KB → Using Intelligent Operations Reports for Capacity Planning
Question #54
An administrator is protecting an application and its data stored on Volume Groups using Protection Domains.
During failover tests, all application VMs restore successfully, but the application data is completely missing.
How can the Protection Domain configuration be adjusted to avoid this issue in the future? (Choose two.)
- A . Select the "Auto protect related entities" checkbox.
- B . Manually add Volume Groups to Protected Entities.
- C . Place Volume Groups in a separate Protection Domain.
- D . Use application-consistent snapshots.
Correct Answer: A, B
A, B
Explanation:
Protection Domains (PDs) in Nutanix ensure that entire applications and their associated data are protected during failover. However, Volume Groups (VGs) are not automatically included unless explicitly configured.
Option A (Select "Auto protect related entities") is correct:
This setting ensures that associated Volume Groups, networks, and other dependencies are included in the Protection Domain automatically.
Without enabling this, only the VM itself would be protected, leading to missing application data upon failover.
Option B (Manually add Volume Groups to Protected Entities) is correct:
If "Auto protect related entities" is not enabled, the administrator must manually add Volume Groups to the Protection Domain.
This ensures that both VMs and their attached Volume Groups are replicated and recovered together.
Option C (Place Volume Groups in a separate Protection Domain) is incorrect:
Separating Volume Groups into a different PD does not guarantee they failover together with VMs.
It is best practice to keep related VMs and Volume Groups in the same PD.
Option D (Use application-consistent snapshots) is incorrect:
While application-consistent snapshots improve data integrity, they do not fix missing Volume
Groups in failover scenarios.
Reference: Nutanix Disaster Recovery Guide → Protection Domain Configuration and Volume Groups
Nutanix KB → Ensuring Volume Groups Are Included in Disaster Recovery Failovers
A, B
Explanation:
Protection Domains (PDs) in Nutanix ensure that entire applications and their associated data are protected during failover. However, Volume Groups (VGs) are not automatically included unless explicitly configured.
Option A (Select "Auto protect related entities") is correct:
This setting ensures that associated Volume Groups, networks, and other dependencies are included in the Protection Domain automatically.
Without enabling this, only the VM itself would be protected, leading to missing application data upon failover.
Option B (Manually add Volume Groups to Protected Entities) is correct:
If "Auto protect related entities" is not enabled, the administrator must manually add Volume Groups to the Protection Domain.
This ensures that both VMs and their attached Volume Groups are replicated and recovered together.
Option C (Place Volume Groups in a separate Protection Domain) is incorrect:
Separating Volume Groups into a different PD does not guarantee they failover together with VMs.
It is best practice to keep related VMs and Volume Groups in the same PD.
Option D (Use application-consistent snapshots) is incorrect:
While application-consistent snapshots improve data integrity, they do not fix missing Volume
Groups in failover scenarios.
Reference: Nutanix Disaster Recovery Guide → Protection Domain Configuration and Volume Groups
Nutanix KB → Ensuring Volume Groups Are Included in Disaster Recovery Failovers
Question #55
An administrator started an LCM upgrade of the AHV hosts but realized that the upgrade would exceed the planned maintenance window.
Which feature should be leveraged to prevent additional updates from occurring?
- A . Cancel the LCM tasks via the Ergon command line (ecli).
- B . Run the lcm_task_cleanup.py script.
- C . Restart Genesis on the cluster to restart the LCM service.
- D . Use the Stop Update feature in LCM.
Correct Answer: D
D
Explanation:
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
D
Explanation:
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
Question #56
After adding new workloads, the Overall Runway is now below 365 days, but the scenario still shows the cluster is in good shape.
Why?
- A . Because Storage Runway is still good.
- B . Because new workloads are sustainable.
- C . Because there are recommended resources.
- D . Because the Target is 1 month.
Correct Answer: B
B
Explanation:
A cluster runway below 365 days does not necessarily indicate an issue if Intelligent Operations determines that workloads are sustainable.
Option B (Because new workloads are sustainable) is correct:
Nutanix analyzes resource trends and marks clusters as healthy if new workloads are within projected capacity.
Option A (Storage Runway is still good) is incorrect:
Storage is one component, but CPU and memory also affect runway calculations.
Option C (Recommended resources) is incorrect:
Recommendations help optimize capacity, but do not define cluster health.
Option D (Target is 1 month) is incorrect:
The scenario’s target window does not impact the actual runway calculation.
Reference: Nutanix Prism Central Guide → Capacity Planning & Runway Analysis Nutanix KB → Understanding Capacity Runway and Workload Sustainability
B
Explanation:
A cluster runway below 365 days does not necessarily indicate an issue if Intelligent Operations determines that workloads are sustainable.
Option B (Because new workloads are sustainable) is correct:
Nutanix analyzes resource trends and marks clusters as healthy if new workloads are within projected capacity.
Option A (Storage Runway is still good) is incorrect:
Storage is one component, but CPU and memory also affect runway calculations.
Option C (Recommended resources) is incorrect:
Recommendations help optimize capacity, but do not define cluster health.
Option D (Target is 1 month) is incorrect:
The scenario’s target window does not impact the actual runway calculation.
Reference: Nutanix Prism Central Guide → Capacity Planning & Runway Analysis Nutanix KB → Understanding Capacity Runway and Workload Sustainability
Question #57
An administrator needs to optimize a VM’s storage by leveraging compression features. The VM’s vDisks are currently stored in a default storage container with no optimizations enabled.
How should the administrator proceed?
- A . Migrate vDisks to the Production storage container.
- B . Recreate the VM in the Production storage container and copy data.
- C . Migrate the VM to the Production storage container.
- D . Recreate the vDisk in the Production storage container and copy data.
Correct Answer: A
A
Explanation:
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-disruptive and allows compression settings to be applied dynamically.
Option B (Recreate the VM) is incorrect:
Rebuilding the VM is unnecessary and would cause downtime.
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 is manual and time-consuming, while Nutanix provides an automated approach.
Reference: Nutanix Storage Optimization Guide → Enabling Compression on Existing vDisks Nutanix KB → Migrate vDisks Between Storage Containers for Optimization
A
Explanation:
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-disruptive and allows compression settings to be applied dynamically.
Option B (Recreate the VM) is incorrect:
Rebuilding the VM is unnecessary and would cause downtime.
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 is manual and time-consuming, while Nutanix provides an automated approach.
Reference: Nutanix Storage Optimization Guide → Enabling Compression on Existing vDisks Nutanix KB → Migrate vDisks Between Storage Containers for Optimization
Question #58
What is supported for creating a VM Template in Nutanix?
- A . VM is protected by Protection Domain-based DR.
- B . VM is an agent or a Prism Central VM.
- C . VM has disks located on RF2 containers.
- D . VM runs on the ESXi hypervisor.
Correct Answer: C
C
Explanation:
VM templates in Nutanix are supported only when the VM’s disks reside on storage containers configured with Replication Factor 2 (RF2) or higher.
Option C (VM has disks on RF2 containers) is correct:
VM templates require a minimum RF2 for fault tolerance.
RF1 containers do not meet Nutanix best practices for VM templates.
Option A is incorrect:
VMs protected by Protection Domains can be cloned, but this is different from creating a VM template.
Option B is incorrect:
Agent VMs (e.g., Witness VMs) or Prism Central cannot be used as VM templates.
Option D is incorrect:
Nutanix VM templates are natively supported on AHV, not ESXi.
Reference: Nutanix VM Management Guide → Creating and Managing VM Templates Nutanix KB → Storage Requirements for VM Templates
C
Explanation:
VM templates in Nutanix are supported only when the VM’s disks reside on storage containers configured with Replication Factor 2 (RF2) or higher.
Option C (VM has disks on RF2 containers) is correct:
VM templates require a minimum RF2 for fault tolerance.
RF1 containers do not meet Nutanix best practices for VM templates.
Option A is incorrect:
VMs protected by Protection Domains can be cloned, but this is different from creating a VM template.
Option B is incorrect:
Agent VMs (e.g., Witness VMs) or Prism Central cannot be used as VM templates.
Option D is incorrect:
Nutanix VM templates are natively supported on AHV, not ESXi.
Reference: Nutanix VM Management Guide → Creating and Managing VM Templates Nutanix KB → Storage Requirements for VM Templates
Question #59
An administrator has configured AHV Metro Availability with Witness and is testing failover scenarios.
During testing, the administrator disconnects the primary and recovery clusters but Prism Central remains connected to the recovery site.
What are two expected system behaviors? (Choose two.)
- A . Guest VM I/O operations pause (freeze) until connectivity is restored.
- B . Guest VM I/O operations pause (freeze) until connectivity between Prism Central and the primary site is restored.
- C . Guest VMs failover automatically to the recovery cluster.
- D . Guest VMs continue to run on the primary cluster.
Correct Answer: A, C
A, C
Explanation:
When connectivity between Metro clusters is lost, Nutanix Metro Availability ensures data integrity using Witness for automatic failover.
Option A (Guest VM I/O operations pause until connectivity is restored) is correct:
Metro Availability enforces data consistency, so I/O operations pause until failover is confirmed.
Option C (Guest VMs failover automatically to the recovery cluster) is correct:
The Witness VM detects the failure and initiates an automatic failover to the secondary cluster.
Option B is incorrect:
Prism Central does not control VM failover in Metro Availability.
Option D is incorrect:
The primary cluster is unreachable, so VMs cannot continue running there.
Reference: Nutanix Metro Availability Guide → How Witness Handles Failover Scenarios Nutanix KB → I/O Freezing and Failover Behavior in Metro Clusters
A, C
Explanation:
When connectivity between Metro clusters is lost, Nutanix Metro Availability ensures data integrity using Witness for automatic failover.
Option A (Guest VM I/O operations pause until connectivity is restored) is correct:
Metro Availability enforces data consistency, so I/O operations pause until failover is confirmed.
Option C (Guest VMs failover automatically to the recovery cluster) is correct:
The Witness VM detects the failure and initiates an automatic failover to the secondary cluster.
Option B is incorrect:
Prism Central does not control VM failover in Metro Availability.
Option D is incorrect:
The primary cluster is unreachable, so VMs cannot continue running there.
Reference: Nutanix Metro Availability Guide → How Witness Handles Failover Scenarios Nutanix KB → I/O Freezing and Failover Behavior in Metro Clusters
Question #60
An administrator configured a remote site for Protection Domain replication, but network performance and stability are impacted.
How can the remote site configuration be adjusted to fix the issue?
- A . Configure Network Address Translation (NAT) between the two Nutanix clusters.
- B . Configure the Protection Domain with many-to-many replication.
- C . Configure a Bandwidth Throttling Policy.
- D . Configure the remote Cluster VIP as a proxy.
Correct Answer: C
C
Explanation:
Network performance issues during replication can be mitigated using Bandwidth Throttling to control traffic spikes.
Option C (Configure a Bandwidth Throttling Policy) is correct:
Bandwidth Throttling ensures that replication does not saturate the network, especially during peak usage hours.
This is particularly useful for low-bandwidth connections between remote sites.
Option A (Configure NAT) is incorrect:
NAT is not required for remote site replication between Nutanix clusters.
Option B (Many-to-Many Replication) is incorrect:
This does not directly address network performance and may increase traffic load.
Option D (Remote Cluster VIP as Proxy) is incorrect:
VIP configurations help with load balancing but do not resolve bandwidth issues.
Reference: Nutanix Protection Policies Guide → Bandwidth Throttling for Remote Site Replication Nutanix KB → Optimizing Network Performance for Disaster Recovery
C
Explanation:
Network performance issues during replication can be mitigated using Bandwidth Throttling to control traffic spikes.
Option C (Configure a Bandwidth Throttling Policy) is correct:
Bandwidth Throttling ensures that replication does not saturate the network, especially during peak usage hours.
This is particularly useful for low-bandwidth connections between remote sites.
Option A (Configure NAT) is incorrect:
NAT is not required for remote site replication between Nutanix clusters.
Option B (Many-to-Many Replication) is incorrect:
This does not directly address network performance and may increase traffic load.
Option D (Remote Cluster VIP as Proxy) is incorrect:
VIP configurations help with load balancing but do not resolve bandwidth issues.
Reference: Nutanix Protection Policies Guide → Bandwidth Throttling for Remote Site Replication Nutanix KB → Optimizing Network Performance for Disaster Recovery