NCP-MCI-7.5 Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI) 7.5 Free Practice Exam Questions (2026 Updated)

Nutanix documentation for enabling Marketplace in Prism Central explicitly states that a unique data services IP address (DSIP) must be configured on the Prism Element cluster that hosts Prism Central. This is a hard prerequisite for Marketplace enablement and application deployment workflows. In exam terms, the presence of DSIP is not optional convenience; it is a setup requirement Nutanix calls out directly before Marketplace can be used. ( Nutanix )

The other answers are not Marketplace prerequisites in the same direct sense. SMTP is useful for email notifications, LDAP for external authentication, and LACP for network design, but none of those is the documented enabling requirement for Marketplace. Nutanix separates platform application management prerequisites from general infrastructure best practices, and DSIP falls into the former category. So when the exam asks what must already be in place on the Prism Element cluster before enabling Marketplace, the correct answer is A: Data services IP must be configured. ( Nutanix )

Nutanix documentation for enabling load balancing of vDisks in a volume group states that vDisk load balancing is enabled by default for volume groups attached to VMs by using a Data Services IP address. That is the exact behavior this question asks about: how to make load balancing happen by default rather than managing it manually each time. Therefore D is the correct answer. ( portal.nutanix.com , portal.nutanix.com )

The other answers may relate to supported limits or guest best practices, but they do not describe the default-enablement mechanism. Nutanix intentionally ties this behavior to the DSIP-based attachment model, which simplifies pathing and discovery while automatically enabling the balancing behavior. So for a study guide aligned to Nutanix docs, D is the authentic answer.

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 )

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 documentation for Erasure Coding is explicit: a cluster must have a minimum of four nodes to enable erasure coding, and for RF2 the minimum remains four nodes. Nutanix further explains that RF3 with erasure coding requires six nodes, which helps distinguish the two thresholds clearly for exam purposes. Since the question asks specifically about Replication Factor 2 and Erasure Coding, the minimum supported node count is 4. ( Nutanix )

This question is testing one of the most common node-count rules in Nutanix storage efficiency. A three-node cluster can provide RF2 storage, but that does not automatically mean erasure coding is available there. Erasure coding introduces its own resiliency and stripe-width requirements, and Nutanix sets the minimum at four nodes for RF2. The values 5 and 6 are distractors meant to confuse RF2 and RF3 rules. Because the official requirement is four nodes for RF2 EC, the correct answer is B. ( Nutanix )

The uploaded source file shows the answer key as B, but the supporting exhibit or calculation context is missing from the provided document, so a full mathematical derivation cannot be verified from the question bank itself. Because of that missing context, the safest exam-faithful response is to preserve the source answer of 1125 IOPS while being transparent that the exact intermediate values used to reach that number are not visible in the provided material.

From a Nutanix policy perspective, IOPS throttling is implemented through storage policies to control or cap workload consumption and prevent noisy-neighbor impact. The conceptual goal is to set a value high enough to accommodate the intended steady-state workload while still enforcing policy boundaries. In practice, administrators usually choose a value above the observed average to allow normal variance, bursts, and scheduler overhead rather than matching the average exactly. That design logic is consistent with an answer larger than 800 IOPS. Given the choices and the source key, 1125 is the preserved answer for this batch, but this is one of the questions where the missing exhibit should ideally be restored before using it as a final study reference. ( Nutanix )

In Prism Central, Runway Analysis is not a simple reading of current utilization; it is a forecast based on historical consumption trends. Nutanix documentation explains that capacity planning and runway use machine learning and historical resource behavior to estimate when CPU, memory, or storage will run out. That means a cluster can still show only 60% memory used today and yet have a short memory runway if the memory-consumption trend has been climbing steadily and rapidly over recent history. In this scenario, the most likely reason for only 12 days of runway is sustained growth in memory use over the historical observation period. ( Nutanix )

The distractors do not fit the documented behavior as well. Nutanix does support scenario modeling, but a low runway in the standard view is primarily a forecast outcome, not a default penalty for missing history or a result of guaranteed HA mode by itself. HA reservations can reduce available effective capacity, but the wording of the question points to forecasting logic rather than static reservation math. Since Nutanix runway is based on actual consumption trends, the answer that best explains a low runway despite moderate present-day utilization is that memory usage has been continuously increasing, which is option B. ( Nutanix )

Nutanix documentation on rebuild capacity reservation and resilient capacity emphasizes that some storage space must remain effectively protected so the cluster can recover from failures and maintain resiliency. If a cluster consumes all capacity beyond that protected threshold, it can reach a point where it no longer safely accepts writes because continuing to do so would violate resiliency guarantees. The symptoms in the question—stopped accepting writes and VM outages—align with a cluster hitting its resilient capacity limit, not merely an EC optimization limit. ( Nutanix )

This distinction matters. Erasure coding limits affect efficiency opportunities, but they do not by themselves explain the cluster refusing writes. A degraded container after a node failure may contribute to pressure, but the wording centers on cluster-wide behavior after rebuild-capacity reservation is enabled. Nutanix’s resiliency logic is designed to protect the cluster from entering an unsafe state, and one enforcement mechanism is to stop admitting additional writes when resilient capacity has been exhausted. Therefore, the most likely cause is C: the cluster has reached its resilient capacity limit. ( Nutanix )

The decisive metric in the iostat output is %iowait = 83.20. In Linux performance interpretation, such a high iowait value means the CPU is spending most of its time waiting for disk I/O operations to complete rather than actively executing user or system work. On a Nutanix CVM, that strongly suggests the storage path is the bottleneck at that moment, whether due to backend disk saturation, contention, or broader storage subsystem latency. Since user CPU and steal are both low, the issue is not primarily compute pressure or hypervisor scheduling contention. Therefore, A is the most accurate description. ( Nutanix )

This is a classic Nutanix troubleshooting interpretation question. If the output had shown high %steal, then hypervisor contention would be a stronger candidate. If %system and %user were both very high, compute load from services would be more likely. But with the overwhelming majority of time in iowait, the signal points toward delayed storage completion. In operational terms, the next steps would usually involve checking CVM disk metrics, Stargate performance, storage latency, and possibly the health of the underlying drives. The evidence in the output supports a storage wait condition, which is exactly what option A says. ( Nutanix )

Nutanix documentation for Prism Central deployment states that single Prism Central VM deployments are supported in Small, Large, or X-Large sizes, and that a single-VM deployment can later be scaled out. Since X-Small is not the supported minimum deployment size in this documented model, the minimum supported size is Small. That makes A correct.

This question is really checking whether the administrator understands the starting point for a scale-out-capable Prism Central design. The existence of larger sizes does not change the minimum supported entry point. Nutanix’s documentation is explicit that a single Prism Central VM can begin at Small and later be expanded if more scale or resiliency is needed. Therefore, for a single-node Prism Central deployment with future scale-out potential, the correct answer is Small.

For AHV, when enabling LACP, Nutanix documentation specifies the Active-Active bond type, also described as balance-tcp. Nutanix explicitly ties LACP and link aggregation behavior to the Active-Active configuration and notes that this configuration sets LACP fallback to Active-Backup on AHV hosts. That makes C the correct bond type for an LACP-enabled design. ( Nutanix Portal )

It is also important to understand why Active-Active with MAC Pinning is wrong here. Nutanix documentation states that the MAC-pinning / balance-slb style must not be used with link aggregation protocols such as LACP. So even though both options sound like they distribute traffic, only one is compatible with LACP. Active-Backup provides redundancy, but not the LACP behavior being requested. “No Uplink Bond” obviously does not meet the requirement. Even without the missing exhibit from the uploaded file, the Nutanix networking documentation makes the intended answer clear: Active-Active is the bond type used when enabling LACP on AHV. ( Nutanix Portal )

A required RPO of 5 minutes immediately points to NearSync replication, because Nutanix documents NearSync protection policies as supporting recovery points in 1–15 minute intervals. The second requirement—automatically protect new mission-critical VMs—points to a Protection Policy approach in Prism Central, because protection policies can use categories and policy-based assignment to scale protection dynamically as new matching VMs are added. Combining those two requirements makes Protection Policy with NearSync replication the correct answer. ( Nutanix )

Protection Domains can support NearSync in older or alternate workflows, but the phrase “new mission critical VMs should be automatically protected” is the clue that pushes this question toward policy-based protection rather than manually maintained membership. Asynchronous replication also fails the first requirement because its RPO target is not the 5-minute class represented by NearSync. Nutanix’s modern DR design encourages policy-driven protection for scalable, category-based administration. Therefore B is the best fit for both the RPO and automatic-inclusion requirements. ( Nutanix )