NCP-MCI-7.5 Exam Questions Tutorials

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 )

Moving a running VM between hosts in the same cluster without downtime is the exact purpose of live migration in AHV. Nutanix AHV administration guidance treats live migration as the supported mechanism for relocating active workloads between hosts while maintaining service continuity, subject to any migration restrictions such as passthrough devices or CPU compatibility constraints. Because the VM must remain powered on and operating during the move, D. Live migrate within the cluster is the correct answer.

The other options are all recovery or duplication workflows, not mobility workflows. Restoring from a backup or recovery point creates interruption and changes the task from migration to recovery. Cloning from a snapshot creates another copy rather than moving the currently running VM. Nutanix intentionally distinguishes VM recovery operations from VM mobility operations. Since the requirement is in-place movement of a live workload within the cluster, the correct and most direct method is live migration. Therefore D is the authentic Nutanix answer.

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 )

To receive an alert earlier, the administrator must lower the threshold at which the alert’s warning state is triggered. Nutanix alerting works by comparing utilization against configured warning and critical thresholds. If the threshold is lowered, the system reaches it sooner, which gives the administrator more lead time before the environment becomes capacity-constrained. Among the given options, the one that directly performs that function is decreasing the Storage Container Space Usage Exceeded alert Warning threshold, which is option C.

The other choices are weaker or misaligned. There is no meaningful “increase frequency” adjustment that changes when capacity is considered low; it would only change how often checks occur, not the trigger point. Changing the critical threshold does not provide earlier warning notice, which is what the question asks for. The wording also points more naturally to a threshold-based action rather than enabling a different alert family. In Nutanix monitoring, earlier warnings come from making the warning trigger more conservative. Therefore C is the best answer because it causes the alert to fire at a lower usage percentage and provides earlier operational notice.