NCP-MCA Exam Dumps : Nutanix Certified Professional - Multicloud Automation (NCP-MCA 6.10) Exam

In Nutanix Intelligent Operations (X-Play), a Playbook action can have a status of"Skipped"in the execution history. This status is specific and distinct from "Failed."

Conditional Execution:Administrators can configureConditionson individual Playbook actions (e.g., "Only run this step if the Alert Severity == Critical" or "Only if entity name contains 'Prod'").

The Cause:If the Playbook triggers successfully but the specific criteria for the notification step are not met during execution, X-Playskipsthat specific action while effectively completing the Playbook run.

If the service were down (Option B) or the configuration invalid (Option A), the step would typically report a"Failed"status, not "Skipped."

To successfully enable and deploy Nutanix Self-Service (formerly Calm), thePrism Centralinstance must have a configuredFully Qualified Domain Name (FQDN).

Requirement:The Self-Service engine (Calm) runs as a set of containerized microservices. These services rely on internal certificates for secure communication and ingress routing.

Validation:During the enablement of the Self-Service feature, Prism Central validates that an FQDN is configured. If only an IP address is used, the enablement process may fail or the services may not function correctly because the certificate generation process requires a valid hostname to establish trust.

Contrast:While Network Segmentation (A) and SNMP (C) are supported features, they are not mandatory prerequisites for the basic deployment of the Self-Service engine.

Nutanix Disaster Recovery usesProtection Policiesto automate replication. These policies are applied to VMs dynamically based onCategories. To protecteveryVM from both blueprints described, the administrator must select a category that iscommon to bothsets of VMs.

Blueprint 1 Categories:OSType: Windows, AppType:IIS

Blueprint 2 Categories:OSType: Windows, Environment:Dev

Commonality:The category OSType: Windows is assigned in both blueprints.

Configuration:By creating a Protection Policy that targets the category OSType: Windows, any VM deployed fromeitherblueprint will automatically inherit this tag. Consequently, the Disaster Recovery engine will immediately detect the new VM and begin replicating it according to the policy (Asynchronous, 1 hour) without manual intervention.

Options B and D would only protect a subset of the VMs (only IIS servers or only Dev workstations, respectively).