Nutanix Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI) 7.5 NCP-MCI-7.5 Exam Dumps: Updated Questions & Answers (April 2026)

Nutanix DR documentation for test failover states that recovered test VMs are brought up in a test virtual network at the recovery AZ, separate from production. Nutanix also documents that when multiple recovery directions or multiple recovery AZs are involved, recovery planning should be created per target direction and the required production and test network mappings need to exist for the recovery plan being tested. If recovery must be tested in both directions between the two clusters, each side effectively needs a production network and a test network. That makes two production networks and two test networks the most complete and correct answer.

This question is really about symmetry. One-direction failover testing can be done with a simpler mapping set, but the moment the requirement says test recovery in both directions, each cluster must be able to act as a recovery site and provide an isolated test-recovery network. That is why a single shared test network is not the best answer here. Nutanix’s recovery-plan structure and test-failover guidance support this interpretation. Therefore C is the correct and most practical answer.

Nutanix AHV High Availability documentation states that if a host remains disconnected for 40 seconds, VMs on that host can be automatically restarted based on HA settings. The same Nutanix documentation also explains that AHV uses the segment-based reservation method for guaranteed VM High Availability and that the older host-based reservation method is deprecated. Since the question asks which method should be used in that HA context, the correct answer is segment-based reservation method. ( Nutanix )

The wording about root filesystem corruption and read-only state appears to mix HA behavior with host health validation, but among the listed choices only segment-based reservation is an actual current Nutanix HA reservation method documented for this purpose. “Root file system corruption method” and “scheduler-based reservation method” are not valid Nutanix reservation methods. Because Nutanix explicitly says Acropolis uses segment-based reservation for guaranteed HA, that is the best and supported answer even if the question stem is somewhat awkwardly phrased. Therefore, C is correct. ( Nutanix )

For a standard AHV cluster deployment, each node typically requires one IP for the hypervisor host, one for the Controller VM (CVM), and one for IPMI or management access. Nutanix cluster-creation and expansion documentation repeatedly references entering host, CVM, and IPMI addresses for each node. If the administrator also wants a cluster virtual IP, that adds one additional IP for the cluster VIP. This results in three IPs per node plus one VIP, which is option C. ( Nutanix )

The answer choices with four IPs per node overstate the standard requirement, while the two-VIP choices add an extra VIP not requested in the question. Nutanix documentation for cluster details also distinguishes the per-node addresses from the optional virtual IP used for cluster access. So the clean way to think about this is: per node = host + CVM + IPMI, plus one shared VIP for the cluster. That aligns exactly with C. ( Nutanix )

Nutanix documentation for Updating Capacity Configurations explains that the Reserve Capacity For Failure option determines whether runway analysis should account for the impact of a node failure, and when Auto Detect is selected, Prism Central automatically uses the cluster’s failure assumptions rather than the full unconstrained cluster total. In practical runway terms, that means the calculation reflects the loss of the node whose failure would have the greatest effect on usable capacity. Among the provided options, the best match for that documented logic is D: the runway analysis excludes the resources of the largest node so estimates account for a node failure. ( Nutanix Portal )

This behavior is important because runway is intended to answer “how long until I run out of safe usable capacity,” not just “how long until all raw resources are consumed.” Nutanix therefore lets administrators model capacity while preserving headroom for failure scenarios. The fixed 10% answer is too generic and not how Nutanix documents the option. Storage-only reservation also misses the fact that runway tracks CPU, memory, and storage dimensions. So, based on Nutanix’s Auto Detect wording and the resilience-oriented design of runway planning, D is the most authentic answer. ( Nutanix Portal )

Nutanix supports storage policy–based encryption in Prism Central, which is exactly the right mechanism when only a subset of workloads needs encryption. Nutanix documentation explains that in addition to cluster-level encryption, administrators can configure storage policies to encrypt data at rest and apply those policies selectively. Since the PCI-DSS workloads are already logically groupable by category, the proper design is to create a storage policy with encryption enabled and then associate it with the category assigned to those VMs. That makes C correct. ( portal.nutanix.com , portal.nutanix.com , portal.nutanix.com )

Cluster-level encryption would encrypt too much, which violates the requirement to leave general-purpose VMs unencrypted. Guest OS BitLocker is a separate operating-system control, not the Nutanix platform answer being tested here. Container-centric thinking is older and less flexible than policy-based encryption. Nutanix’s policy model is the authentic platform-aligned solution for category-scoped encryption using an external KMS.

Foundation Central is about deployment centralization, not backup, lifecycle upgrades, or automatic registration workflows as its main value proposition. Nutanix documentation describes Foundation Central as a tool that can manage several Foundation instances from a single pane of glass, allowing administrators to create clusters of remote nodes. That statement maps directly to option D. ( Nutanix Portal )

The subtle point here is that the question mentions Marketplace only as the method used to deploy Foundation Central, not as the capability being tested. Once deployed, Foundation Central’s job is to simplify remote cluster creation at scale. It does not replace LCM for software upgrades, nor is its primary role to perform backup and recovery of cluster configurations. Automatic cluster registration may happen as part of broader operational workflows, but it is not the core capability Nutanix emphasizes in the product description. In the context of imaging and deploying many branch-office clusters from a central team, the defining capability is centralized cluster creation and management visibility. That is why D is the right answer. ( Nutanix Portal )

For database workloads, Nutanix documentation distinguishes between crash-consistent and application-consistent recovery points. If the Take App-Consistent Recovery Points option is not selected, the recovery point may capture storage in a crash-consistent state only. For transactional databases, that can lead to corruption, incomplete writes, or recovery issues after restore. Nutanix specifically documents that selecting the app-consistent option creates application-consistent recovery points; if you do not select it, the recovery points are crash-consistent. That makes D the most likely root cause. ( portal.nutanix.com , portal.nutanix.com )

The mention that NGT was checked is important because NGT participation is commonly part of quiesced and app-consistent protection workflows. A high RPO can increase data loss, but it does not by itself explain logical corruption inside the restored database. Category choice and roll-up schedule are also not the primary issue. Nutanix best practice for databases is to ensure application-consistent protection is enabled wherever supported. Therefore D is the correct answer.

The error message is tied to resilience requirements. Nutanix documentation states that Replication Factor 3 requires at least five nodes so data remains online even if two nodes fail concurrently. If removing a node would drop the cluster below the minimum usable-node requirement, Nutanix blocks the operation. The safest and supported way to proceed during a hardware refresh is to add the replacement node first, restore compliant cluster capacity, and then remove the original node. ( Nutanix Portal )

The wrong answers all involve bypassing or weakening resilience inappropriately. Changing cluster or container RF to RF2 just to remove a node would reduce fault tolerance and is not the right answer for a SQL environment where resilience matters. Force-removal is also not the supported operational answer in a healthy refresh workflow. This question tests whether the administrator understands that node lifecycle actions are constrained by Nutanix fault-tolerance rules. When the cluster says it needs at least five usable nodes, the correct action is not to override the rule but to satisfy it by adding capacity first. Therefore A is the correct answer. ( Nutanix Portal )

Nutanix LCM documentation for the pre-check test_ahv_entering_mm_pinned_vms explains that this check identifies VMs that block the host from entering maintenance mode. Nutanix also notes that during host updates, LCM automatically shuts down running non-migratable VMs before updating the host. In practice, VMs using certain pinned or non-migratable features—such as specific agent, passthrough, or unsupported migration cases—must be powered off if they cannot be moved safely. That makes D the best answer. ( portal.nutanix.com , portal.nutanix.com )

The key is that not every special VM can live-migrate in every environment. Credential Guard migration has CPU-generation limitations, and pinned or specialized VMs can still block maintenance. The safest supported action for the listed blocked VMs is to power them off, let the host enter maintenance mode, and then proceed. So D is the right operational answer.

The requirement is straightforward: there is one source site (Site A) and the workload must be replicated to two destination clusters, each with potentially different RPO settings. In Nutanix DR design terminology, that is a one-to-many replication pattern. Nutanix documentation for multisite disaster recovery explains that a single protection policy can include replication schedules to multiple recovery clusters, which is how a source can protect workloads to more than one target with different schedule definitions. That makes D the correct answer.

The other choices describe different topologies. Many-to-One means multiple sources targeting one destination. Many-to-Many is broader bidirectional or multiple-source/multiple-target logic than the question requires. Two-Way-Mirroring is not the correct pattern for one source sending copies outward to two other sites. Nutanix’s protection-policy model is specifically flexible enough to define different replication schedules toward separate destinations, which is why this exact scenario is best labeled One-to-Many. So for an exam-aligned and documentation-consistent answer, D is the right choice.