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 #21
An administrator wants to enable application discovery on a Nutanix cluster to monitor applications.
A Prism Central instance is already configured with sufficient CPU and memory.
What other prerequisites must be met before enabling application discovery? (Choose two.)
- A . Sufficient Prism Central VM resources
- B . Internet connection
- C . API key and key ID
- D . Network controller is enabled
Correct Answer: A, B
A, B
Explanation:
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 needs adequate CPU and memory to process application signatures and discovery data.
Option B (Internet connection) is correct:
Application discovery depends on Nutanix’s cloud database to recognize application patterns.
Option C (API key and key ID) is incorrect:
API keys are not required for automatic application discovery.
Option D (Network controller enabled) is incorrect:
Application discovery does not depend on a network controller feature.
Reference: Nutanix Prism Central Guide → Enabling and Using Application Discovery Nutanix KB → Requirements for Application Discovery in Prism Central
A, B
Explanation:
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 needs adequate CPU and memory to process application signatures and discovery data.
Option B (Internet connection) is correct:
Application discovery depends on Nutanix’s cloud database to recognize application patterns.
Option C (API key and key ID) is incorrect:
API keys are not required for automatic application discovery.
Option D (Network controller enabled) is incorrect:
Application discovery does not depend on a network controller feature.
Reference: Nutanix Prism Central Guide → Enabling and Using Application Discovery Nutanix KB → Requirements for Application Discovery in Prism Central
Question #22
After upgrading Prism Central from PC2022.1 to PC2024.1, an administrator is unable to log in with their IAM domain account.
What is the first troubleshooting step the administrator should take?
- A . Ping the Domain Controller from the CVM.
- B . Ensure port 9441 is open in the firewall.
- C . Validate the trusted signing certificate of the organization.
- D . Log in with a local admin account.
Correct Answer: D
D
Explanation:
After a Prism Central upgrade, IAM authentication settings may require reconfiguration.
Option D (Log in with a local admin account) is correct:
If IAM authentication fails, the local admin account must be used to check domain settings.
Option A (Ping the Domain Controller) is incorrect:
Network connectivity is important, but the issue is likely related to IAM settings, not network reachability.
Option B (Check firewall port 9441) is incorrect:
Port 9441 is used for SSO authentication, but port issues usually result in login delays, not complete failures.
Option C (Validate signing certificate) is incorrect:
While certificates can cause issues, local admin login should always work.
Reference: Nutanix KB → Troubleshooting IAM Login Issues After a Prism Central Upgrade Nutanix Documentation → Managing User Authentication and IAM Integration
D
Explanation:
After a Prism Central upgrade, IAM authentication settings may require reconfiguration.
Option D (Log in with a local admin account) is correct:
If IAM authentication fails, the local admin account must be used to check domain settings.
Option A (Ping the Domain Controller) is incorrect:
Network connectivity is important, but the issue is likely related to IAM settings, not network reachability.
Option B (Check firewall port 9441) is incorrect:
Port 9441 is used for SSO authentication, but port issues usually result in login delays, not complete failures.
Option C (Validate signing certificate) is incorrect:
While certificates can cause issues, local admin login should always work.
Reference: Nutanix KB → Troubleshooting IAM Login Issues After a Prism Central Upgrade Nutanix Documentation → Managing User Authentication and IAM Integration
Question #23
An administrator has been tasked with justifying why Nutanix Disaster Recovery was chosen for a multi-tier application spanning multiple business units.
What is the most efficient way to organize and manage the workloads?
- A . Utilize a VM naming schema that allows sorting
- B . Utilize Categories to organize VMs in Recovery Plans
- C . Utilize a 1:10 ratio of Recovery Plan to VMs
- D . Utilize RESTful APIs to script creation of Recovery Plans
Correct Answer: B
B
Explanation:
Nutanix Categories allow administrators to group related VMs, making Disaster Recovery (DR) planning easier.
Option B (Utilize Categories to organize VMs in Recovery Plans) is correct:
Categories help group VMs based on application tiers (e.g., database, middleware, web servers).
This ensures orderly failover while maintaining application dependencies.
Option A (Naming schema) is incorrect:
Naming conventions help, but they do not provide functional organization in recovery plans.
Option C (1:10 Recovery Plan to VMs) is incorrect:
The ratio depends on business requirements, not a fixed number.
Option D (RESTful APIs) is incorrect:
Automation is useful, but it does not replace proper VM grouping via categories.
Reference: Nutanix Disaster Recovery Guide → Using Categories for DR Management Nutanix KB → Organizing VMs for Disaster Recovery Planning
B
Explanation:
Nutanix Categories allow administrators to group related VMs, making Disaster Recovery (DR) planning easier.
Option B (Utilize Categories to organize VMs in Recovery Plans) is correct:
Categories help group VMs based on application tiers (e.g., database, middleware, web servers).
This ensures orderly failover while maintaining application dependencies.
Option A (Naming schema) is incorrect:
Naming conventions help, but they do not provide functional organization in recovery plans.
Option C (1:10 Recovery Plan to VMs) is incorrect:
The ratio depends on business requirements, not a fixed number.
Option D (RESTful APIs) is incorrect:
Automation is useful, but it does not replace proper VM grouping via categories.
Reference: Nutanix Disaster Recovery Guide → Using Categories for DR Management Nutanix KB → Organizing VMs for Disaster Recovery Planning
Question #24
An administrator needs to configure NTP on Prism Central running on a Hyper-V cluster.
How should the administrator complete this task?
- A . Add an external NTP server.
- B . Add the DNS server IP.
- C . Add a server with a DNS hostname.
- D . Add the IP of the Domain Controller.
Correct Answer: A
A
Explanation:
Nutanix requires that all cluster components synchronize time using an external NTP (Network Time Protocol) server.
Option A (Adding an external NTP server) is correct because Nutanix best practices recommend using an external time source to prevent clock drift between cluster nodes.
Option B (DNS server IP) is incorrect: A DNS server does not provide NTP services.
Option C (Server with DNS hostname) is incorrect unless the DNS hostname resolves to an NTP server.
Option D (IP of the Domain Controller) is incorrect because not all domain controllers provide NTP
services unless explicitly configured.
Reference: Nutanix Best Practices: NTP Configuration for Hyper-V Clusters
Nutanix KB: Ensuring Proper Time Synchronization Across Cluster Nodes
Nutanix Documentation: Prism Central NTP Settings Configuration
A
Explanation:
Nutanix requires that all cluster components synchronize time using an external NTP (Network Time Protocol) server.
Option A (Adding an external NTP server) is correct because Nutanix best practices recommend using an external time source to prevent clock drift between cluster nodes.
Option B (DNS server IP) is incorrect: A DNS server does not provide NTP services.
Option C (Server with DNS hostname) is incorrect unless the DNS hostname resolves to an NTP server.
Option D (IP of the Domain Controller) is incorrect because not all domain controllers provide NTP
services unless explicitly configured.
Reference: Nutanix Best Practices: NTP Configuration for Hyper-V Clusters
Nutanix KB: Ensuring Proper Time Synchronization Across Cluster Nodes
Nutanix Documentation: Prism Central NTP Settings Configuration
Question #25
When expanding a cluster, what is required to automatically discover new nodes?
- A . New nodes must have the same hypervisor version.
- B . IPv6 multicast must be allowed on physical switches.
- C . New nodes must have the same AOS version.
- D . IPv4 multicast must be allowed on physical switches.
Correct Answer: D
D
Explanation:
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.
Reference: Nutanix Best Practices → Cluster Expansion & Auto-Discovery
Nutanix KB → Why Nutanix Requires IPv4 Multicast for Node Discovery
D
Explanation:
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.
Reference: Nutanix Best Practices → Cluster Expansion & Auto-Discovery
Nutanix KB → Why Nutanix Requires IPv4 Multicast for Node Discovery
Question #26
An administrator is configuring a replication schedule on multiple remote locations deployed using a single-node cluster. The goal is to achieve the lowest possible RPO (Recovery Point Objective).
How should the administrator configure the replication schedule?
- A . Configure NearSync replication.
- B . Configure a schedule for 16 minutes up to 59 minutes.
- C . Configure Async replication.
- D . Configure a schedule for 1 minute up to 15 minutes.
Correct Answer: D
D
Explanation:
Nutanix NearSync replication provides the lowest RPO (as low as 1 minute) and is the best option for minimizing data loss in DR scenarios.
Option D (Configure a schedule for 1 minute up to 15 minutes) is correct:
NearSync allows an RPO as low as 1 minute, providing near-continuous data protection.
This is ideal for mission-critical applications where minimal data loss is required.
Option A (Configure NearSync) is incorrect:
While NearSync is the best choice, just enabling it is not enough―the schedule must be set to 1-15 minutes.
Option B (16 to 59 minutes) is incorrect:
NearSync operates within a 1-15 minute range. If set above 15 minutes, it defaults to Async replication.
Option C (Async replication) is incorrect:
Async replication typically has an RPO of 1 hour or more, which does not meet the lowest RPO
requirement.
Reference: Nutanix Protection Policies Guide → NearSync vs. Async Replication Nutanix Bible → RPO and RTO in Disaster Recovery
Nutanix KB → Configuring NearSync Replication for Single-Node Clusters
D
Explanation:
Nutanix NearSync replication provides the lowest RPO (as low as 1 minute) and is the best option for minimizing data loss in DR scenarios.
Option D (Configure a schedule for 1 minute up to 15 minutes) is correct:
NearSync allows an RPO as low as 1 minute, providing near-continuous data protection.
This is ideal for mission-critical applications where minimal data loss is required.
Option A (Configure NearSync) is incorrect:
While NearSync is the best choice, just enabling it is not enough―the schedule must be set to 1-15 minutes.
Option B (16 to 59 minutes) is incorrect:
NearSync operates within a 1-15 minute range. If set above 15 minutes, it defaults to Async replication.
Option C (Async replication) is incorrect:
Async replication typically has an RPO of 1 hour or more, which does not meet the lowest RPO
requirement.
Reference: Nutanix Protection Policies Guide → NearSync vs. Async Replication Nutanix Bible → RPO and RTO in Disaster Recovery
Nutanix KB → Configuring NearSync Replication for Single-Node Clusters
Question #27
Due to application requirements, an administrator needs to support a multicast configuration in an AHV cluster.
Which AHV feature can be used to optimize network traffic so that multicast traffic is only forwarded to the VMs that need to receive it?
- A . LACP
- B . UDP
- C . IGMP Snooping
- D . Network Segmentation
Correct Answer: C
C
Explanation:
Multicast traffic can generate unnecessary overhead if it is not properly managed. IGMP Snooping (Option C) ensures that multicast packets are only sent to VMs that have requested them, rather than broadcasting to all VMs.
Option C (IGMP Snooping) is correct:
It reduces unnecessary multicast traffic by ensuring that only subscribed VMs receive the packets.
It is supported natively in AHV networking.
Option A (LACP) is incorrect:
Link Aggregation Control Protocol (LACP) improves bandwidth and redundancy but does not control multicast traffic.
Option B (UDP) is incorrect:
UDP (User Datagram Protocol) is a transport protocol, not a network optimization feature.
Option D (Network Segmentation) is incorrect:
Segmentation (VLANs, VPCs) isolates networks but does not optimize multicast traffic specifically.
Reference: Nutanix AHV Networking Guide → Enabling IGMP Snooping Nutanix Bible → Network Traffic Optimization in AHV Nutanix KB → Best Practices for Multicast Traffic in AHV
C
Explanation:
Multicast traffic can generate unnecessary overhead if it is not properly managed. IGMP Snooping (Option C) ensures that multicast packets are only sent to VMs that have requested them, rather than broadcasting to all VMs.
Option C (IGMP Snooping) is correct:
It reduces unnecessary multicast traffic by ensuring that only subscribed VMs receive the packets.
It is supported natively in AHV networking.
Option A (LACP) is incorrect:
Link Aggregation Control Protocol (LACP) improves bandwidth and redundancy but does not control multicast traffic.
Option B (UDP) is incorrect:
UDP (User Datagram Protocol) is a transport protocol, not a network optimization feature.
Option D (Network Segmentation) is incorrect:
Segmentation (VLANs, VPCs) isolates networks but does not optimize multicast traffic specifically.
Reference: Nutanix AHV Networking Guide → Enabling IGMP Snooping Nutanix Bible → Network Traffic Optimization in AHV Nutanix KB → Best Practices for Multicast Traffic in AHV
Question #28
An administrator has been asked to calculate baseline Capacity Runway on a newly registered AHV cluster.
The cluster has been running for 16 days, but no runway projections are displayed.
Why are no Capacity Runway projections being displayed?
- A . Capacity Planning requires at least 30 days of data.
- B . Capacity Planning requires at least 21 days of data.
- C . Capacity Planning requires at least 3 months of data.
- D . Capacity Planning requires at least 6 months of data.
Correct Answer: B
B
Explanation:
Nutanix Prism Central requires at least 21 days of usage data to generate accurate Capacity Runway projections.
Option B (21 days) is correct:
Until 21 days of data is collected, no runway analysis is available.
Option A (30 days) is incorrect:
30 days is recommended for long-term accuracy, but not required for initial projections.
Option C (3 months) and
Option D (6 months) are incorrect:
Extended data collection helps trend accuracy, but runway calculations begin after 21 days.
Reference: Nutanix Prism Central Guide → Understanding Capacity Runway Calculations Nutanix KB → Why No Capacity Runway Data is Displayed for New Clusters
B
Explanation:
Nutanix Prism Central requires at least 21 days of usage data to generate accurate Capacity Runway projections.
Option B (21 days) is correct:
Until 21 days of data is collected, no runway analysis is available.
Option A (30 days) is incorrect:
30 days is recommended for long-term accuracy, but not required for initial projections.
Option C (3 months) and
Option D (6 months) are incorrect:
Extended data collection helps trend accuracy, but runway calculations begin after 21 days.
Reference: Nutanix Prism Central Guide → Understanding Capacity Runway Calculations Nutanix KB → Why No Capacity Runway Data is Displayed for New Clusters
Question #29
An administrator is trying to delete a protected snapshot but is unable to do so.
What is the most likely cause?
- A . There is an active recovery occurring at that time.
- B . Ransomware has encrypted the snapshot.
- C . There is an approval policy that was denied.
- D . The snapshot has been corrupted.
Correct Answer: A
A
Explanation:
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.
Reference: Nutanix Protection Policies → Snapshot Retention and Deletion Nutanix Bible → Backup & Disaster Recovery Mechanisms Nutanix KB → How to Delete a Snapshot Used in Recovery Plans
A
Explanation:
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.
Reference: Nutanix Protection Policies → Snapshot Retention and Deletion Nutanix Bible → Backup & Disaster Recovery Mechanisms Nutanix KB → How to Delete a Snapshot Used in Recovery Plans
Question #30
An administrator is configuring Nutanix Disaster Recovery (DR) for a cross-hypervisor setup (ESXi to AHV) but finds that guest VMs do not recover properly at the DR location.
What is required for a successful cross-hypervisor DR event?
- A . Utilize delta disks.
- B . Deploy Legacy BIOS boot on hosts within the cluster.
- C . Use raw device mappings.
- D . Nutanix Guest Tools (NGT) must be installed on source guest VMs.
Correct Answer: D
D
Explanation:
For cross-hypervisor DR failover (e.g., ESXi to AHV), Nutanix Guest Tools (NGT) must be installed on VMs to ensure proper configuration and recovery.
Option D (NGT must be installed on source guest VMs) is correct:
NGT ensures correct reconfiguration of VM devices and networking settings during failover.
It handles disk and driver reassignments between ESXi and AHV.
Option A (Utilize delta disks) is incorrect:
Delta disks are used in snapshot optimization, not DR failover.
Option B (Deploy Legacy BIOS boot) is incorrect:
AHV prefers UEFI boot mode, and Legacy BIOS is not a requirement.
Option C (Use raw device mappings) is incorrect:
RDMs are VMware-specific and are not used in AHV failover scenarios.
Reference: Nutanix Disaster Recovery Guide → Cross-Hypervisor Failover Best Practices Nutanix KB → Ensuring VM Compatibility During ESXi to AHV DR
D
Explanation:
For cross-hypervisor DR failover (e.g., ESXi to AHV), Nutanix Guest Tools (NGT) must be installed on VMs to ensure proper configuration and recovery.
Option D (NGT must be installed on source guest VMs) is correct:
NGT ensures correct reconfiguration of VM devices and networking settings during failover.
It handles disk and driver reassignments between ESXi and AHV.
Option A (Utilize delta disks) is incorrect:
Delta disks are used in snapshot optimization, not DR failover.
Option B (Deploy Legacy BIOS boot) is incorrect:
AHV prefers UEFI boot mode, and Legacy BIOS is not a requirement.
Option C (Use raw device mappings) is incorrect:
RDMs are VMware-specific and are not used in AHV failover scenarios.
Reference: Nutanix Disaster Recovery Guide → Cross-Hypervisor Failover Best Practices Nutanix KB → Ensuring VM Compatibility During ESXi to AHV DR