Nutanix NCP-MCI-7.5 - Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI) 7.5

Nutanix documentation explicitly states that in Prism Central, when you are using more than 80% of Prism Central capacity, a red PC Under-provisioned warning icon appears. That means this alert is not describing the managed cluster’s resilient capacity, nor is it about a storage over-provisioning ratio on the Prism Central VM. It is specifically tied to the Prism Central instance itself approaching its own capacity limit. ( Nutanix Portal )

This is a good example of monitoring terminology that can be misleading on the exam. Because the administrator is looking at future resource needs for clusters, it is easy to assume the warning is about the cluster being under-provisioned. However, Nutanix labels this condition as PC Under-provisioned, and the documentation ties it to Prism Central consumption, not the cluster’s resilience threshold or a failed scale-out event. Operationally, the response is to review Prism Central sizing and determine whether scale-out or resizing is required to support the monitored environment. Based on the Nutanix documentation wording, B is the correct answer. ( Nutanix Portal )

Here the uploaded answer key says C, but current Nutanix documentation says the opposite. Nutanix’s Live vDisk Migration Across Storage Containers documentation explicitly states that during an ongoing vDisk migration you cannot perform operations such as clone the VM, resize the VM, or take a snapshot. Nutanix also states, under DR considerations, that you should remove the VM from the protection domain or protection policy, migrate the vDisks, and then add the VM back afterward. That means the actions listed in option C are specifically blocked during vDisk live migration. ( Nutanix Portal )

Because all four answer choices are problematic against the current documentation, this is one of the questions I would flag as flawed in the source bank. The most accurate real-world Nutanix answer is: you should not perform snapshot, clone, resize, or DR policy/protection-domain operations during the migration. So although the uploaded key marks C, the official docs indicate that C is not actually allowed. For your final study document, this question should ideally be corrected or rewritten because the documented AHV behavior does not cleanly support any listed option as a valid “can perform during migration” task. ( Nutanix Portal )

Nutanix separates storage resiliency reservation from compute high availability. For storage, the relevant setting is Rebuild Capacity Reservation, which reserves storage space so the cluster can self-heal and rebuild after node, block, or rack failure. For memory and compute, the relevant concept is High Availability, which reserves or accounts for host resources needed to restart workloads after a host failure. Putting those together gives the combination that best governs the remaining usable storage and memory capacity while preserving fault tolerance. That makes C the most correct answer.

The distractors either use non-standard phrasing or split the concepts incorrectly. “Memory Reservation” by itself is not the standard Nutanix answer when the exam is asking about cluster-wide restart capacity and usable memory after failure accounting. Nutanix administrators think in terms of HA for compute-memory protection and rebuild capacity reservation for storage protection. If the goal is to manage the usable remaining capacity for both storage and memory correctly, the right pair is Rebuild Capacity Reservation and High Availability. Therefore C is the authentic answer.

In Prism Central VM efficiency and behavioral-learning views, Nutanix groups inefficient VMs into categories such as over-provisioned, inactive, bully, and constrained. A constrained VM is one that does not have enough resources for its workload and is therefore experiencing pressure. Nutanix documentation ties constrained status to signs such as CPU readiness, memory swapping, or other stress indicators that show the VM is not adequately provisioned for what it is trying to do. That means the best interpretation is that those VMs are lacking sufficient resources, which is option B. ( Nutanix Portal )

This category is different from the other distractors. An inactive VM is mostly idle and not making meaningful use of its assigned resources. An over-provisioned VM is wasting capacity because it was allocated too much. A VM that is merely “consuming too much CPU” could be a bully VM or simply a busy VM, but that alone does not define the constrained classification. Nutanix uses the constrained label to signal a right-sizing opportunity in the direction of adding or adjusting resources, not reclaiming them. Therefore the most accurate answer is B, because constrained VMs are the ones that are short on sufficient resources for their workload behavior. ( Nutanix Portal )

Nutanix networking documentation is explicit that LACP on AHV requires the Active-Active bond type, also described as balance-tcp. Nutanix further explains that this mode increases host and VM bandwidth utilization beyond a single uplink by balancing VM NIC TCP and UDP sessions across multiple physical adapters. That directly addresses both parts of the requirement in the question: maximizing per-host throughput and per-VM throughput while also providing LACP support. For that reason, B is the correct answer.

The other options do not satisfy the stated requirement. Active-Backup gives redundancy but does not aggregate active bandwidth. Active-Active with MAC pinning (balance-slb) can use multiple adapters without switch configuration, but Nutanix documents that it must not be used with LACP. “No Uplink Bond” obviously cannot maximize throughput or provide aggregation. This question is testing a core AHV networking distinction: if the user explicitly wants LACP, then the answer is always the Active-Active / balance-tcp model. That is why B is the authentic Nutanix answer.

Here the uploaded answer key says D, but official Nutanix documentation supports B. Nutanix documents that for enhanced security of ROBO environments (typically 1- or 2-node clusters), administrators should select Native KMS (remote) for software-based encryption. Nutanix also states in KMS considerations that software encryption using Native KMS is supported for ROBO deployments using the Native KMS (remote) KMS type. Because the question explicitly describes a 2-node ROBO cluster and requires the keys to be stored outside the cluster, the Nutanix-authentic answer is B. Native KMS (remote).

An external KMS is valid in many enterprise encryption designs, but this question is more specific: it asks for the KMS type Nutanix supports and recommends for software encryption on a ROBO cluster. On that narrow requirement, the official docs point to Native KMS (remote) rather than External KMS. So for an authentic study guide aligned to Nutanix documentation, B is the correct answer.

The question is asking for the best balance of capacity efficiency, fault tolerance, and cost control. Nutanix documentation explains that erasure coding is the storage-efficiency mechanism that increases usable capacity by using parity instead of full-copy replication overhead, making it a strong fit when data is relatively cold or infrequently modified. Nutanix also documents that erasure coding requires a minimum of six nodes when using replication factor 3, which corresponds to Fault Tolerance 2 designs. That makes Erasure Coding with six nodes the correct answer.

Deduplication is valuable for certain duplicate-heavy data sets such as VDI or repeated blocks, but the question emphasizes business-critical cold data and a tight budget. In that context, erasure coding provides the more directly documented capacity-efficiency benefit. The five-node options are eliminated by Nutanix’s minimum-node requirement for RF3 erasure coding. Since FT2 implies the higher fault-tolerance design and Nutanix requires six nodes for EC with RF3, A is the correct answer.

The uploaded source file provides the answer choices and key, but the actual requirement or exhibit needed to calculate this answer is missing from the question bank preview. Because of that, the exact sizing logic cannot be fully validated from the provided source material alone. The uploaded file’s answer key shows C, so that is the preserved answer for this batch.

From a Nutanix cluster-planning perspective, questions like this are usually driven by one or more of the following documented factors: usable versus raw capacity, replication factor, reserved rebuild capacity, storage efficiency settings such as compression or erasure coding, and projected runway requirements. Without the missing stem, it is impossible to state which of those variables controlled the calculation here. So for authenticity, the right thing is to be transparent: the source answer is C, but the calculation cannot be proven from the incomplete question as provided. If you later share the missing exhibit or full requirement text for Q69, I can replace this with a fully derived Nutanix-based explanation.

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 )

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.