Nutanix NCP-MCA Exam With Confidence Using Practice Dumps

Comprehensive and Detailed Explanation

Self-Service platform sync allows Prism Central to periodically collect updates from external providers.

Nutanix documentation states that the providers supportingplatform sync with a 20-minute update windoware:

Nutanix (AHV)

VMware (vSphere)

AWS

These environments support the metadata collection necessary for tracking:

IP changes

Disk resizing

VM availability

Thus, the valid set isNutanix, VMware, and AWS, makingOption Ccorrect.

To ensure a Playbook executes at a specific resource threshold (95% Memory), the administrator must link the Playbook to anAlert Policydefined with that specific threshold.

Relationship between Alerts and Playbooks:In Nutanix Intelligent Operations (X-Play), Playbooks are typically event-driven. The most common trigger is theAlerttrigger. The Playbook itself does not define the threshold (e.g., "95%"); rather, it waits for an Alert to fire.

Configuration:The administrator must configure a specific Alert Policy (e.g., "Critical Memory Usage") in Prism Central to trigger when Memory Usage exceeds 95%.

The Solution:By selecting"Change Trigger to be based off Critical Memory Usage Alert"(Option B), the administrator ensures the Playbook reacts specifically to the alert that corresponds to the 95% threshold. If the system was previously alerting at 100%, it implies the Playbook was linked to a different or default policy. Switching the trigger to the correct "Critical" policy (configured for 95%) solves the issue.

Autopilot (Option A):Autopilot is used totuneinfrastructure limits (like adding CPU/Memory) based on KPI targetsaftera playbook runs; it does not trigger the initial remediation playbook itself.

To automate a remediation action (like restarting a VM) based on a specific performance threshold (like CPU usage > 90%), the administrator must useIntelligent Operations (X-Play)with an event-driven trigger.

Alert-Based Trigger:The administrator first ensures there is an Alert Policy in Prism Central for "VM High CPU" configured with a threshold of 90%.

Playbook Configuration:The administrator then creates a Playbook and selects theAlerttrigger (orAlerts Matching Criteriatrigger). They link this trigger to the specific CPU alert policy.

Action:The administrator adds theVM Reboot(or Power Cycle) action to the Playbook.

Result:As soon as the system detects the CPU exceeding 90%, the Alert fires, which immediately triggers the Playbook to reboot the VM without human intervention.

Options A (Scheduled) and C (Manual) do not meet the requirement of "whenever it exceeds," which implies real-time reaction. Option B is incorrect because Project Quotas manage resource allocation limits, not runtime performance monitoring or remediation.