Nutanix Certified Professional NCP-MCA Updated Exam

Plays are event-driven automation workflows that can be triggered by alerts, schedules, or manual actions. They consist of one or more actions that run on specified hosts or clusters. An administrator can obtain the following information from Plays:

• Host where the action runs: Each action in a Play can be configured to run on a specific host or cluster, or on the host or cluster where the alert was triggered. The administrator can view the host or cluster name for each action in the Play details page.
• Execution result status: Each action in a Play has an execution result status that indicates whether the action was successful, failed, skipped, or cancelled. The administrator can view the status for each action in the Play details page, as well as the overall status of the Play.

The other options are incorrect because:

• Start time and end time of each action: Plays do not show the start time and end time of each action, only the duration of the action. The administrator can view the duration for each action in the Play details page, as well as the overall duration of the Play.
• CVM IP where the alert was triggered: Plays do not show the CVM IP where the alert was triggered, only the host or cluster name where the alert was triggered. The administrator can view the host or cluster name for the alert in the Play details page.

References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, Section 1.2
• Nutanix Multicloud Automation Administration (NMCAA) Course, Module 4: X-Play
• Training Spotlight: Nutanix Multicloud Automation Administration (NMCAA), Video 4: X-Play

Autopilot is a feature of Nutanix Calm that allows the administrator to automate the execution of playbooks based on predefined conditions or triggers. Autopilot can optimizethe performance, availability, and cost of applications by applying the appropriate actions in response to events or metrics. Before configuring autopilot, the administrator must be aware of the following limitations12:

• Autopilot never waits for approvals. This means that the administrator must ensure that the playbooks are tested and verified before enabling autopilot. Autopilot will execute the playbooks without any human intervention or confirmation.
• Autopilot feature only applies to metric-based alerts as triggers. This means that the administrator can only use metrics from the Nutanix Prism Central or the Nutanix Karbon clusters as the conditions for triggering the playbooks. Autopilot does not support other types of triggers such as schedules, webhooks, or manual triggers. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 10; Nutanix Calm SaaS User Guide, section 4.3.

According to the Nutanix Prism Central Guide1, categories are key-value pairs that can be assigned to entities such as VMs, images, blueprints, etc. Categories can be used tofilter, group, and manage entities based on their attributes. To review and clean up all existing categories within the Nutanix environment, the administrator should filter on the name, value, entities, and policies of the categories. The name and value of the categories identify the category type and the category value respectively. The entities show how many and which entities are assigned to the category. The policies show how many and which policies are associated with the category. By filtering on these information, the administrator can organize the findings and eliminate unused categories. References:

• 1 Nutanix Prism Central Guide: Categories2