Pass NCP-MCA Exam Guide

A Calm Developer is a role that allows a user to create, update, and execute Playbooks in Calm. A Playbook is a collection of Tasks that can be executed on one or more Targets, such as VMs, applications, or services. A Calm Developer can also create and use Runbooks, Blueprints, and Library items in Calm. A Prism Admin is a role that allows a user to manage the Prism Central instance and its features, such as users, roles, alerts, policies, etc. A Calm Admin is a role that allows a user to manage the Calm service and its settings, such as endpoints, credentials, projects, etc. A Project Admin is a role that allows a user to manage a specific project and its resources, such as applications, Blueprints, Runbooks, etc. References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 14, section 4.1.1
• Nutanix Calm Roles and Permissions
• Nutanix Calm Playbooks

The administrator should use a trigger based on an event when creating a playbook to automate the scaling of the VDI solution. An event trigger is a type of trigger that executes a playbook when a specific event occurs in the Nutanix environment or in a third-party system. An event trigger can be configured to listen to events from various sources, such as Prism alerts, Calm actions, or external webhooks. In this scenario, the administrator can use an event trigger to listen to the webhook from the third-party monitoring tool and execute a playbook that creates additional resources and adds them to the VDI solution.

A trigger based on a REST API is not the best option, because it requires the administrator to manually invoke the playbook using an API call. This is not as efficient or reliable as using an event trigger that automatically executes the playbook when the capacity threshold is reached.

A trigger based on an email is also not the best option, because it requires the administrator to configure an email server and a mailbox to receive the notification from the third-party tool. This adds complexity and overhead to the automation process and may not be as secure or timely as using an event trigger.

A trigger based on an alert is a valid option, but it depends on the availability and compatibility of the Prism alert system with the third-party tool. If the third-party tool can send alerts to Prism, then the administrator can use an alert trigger to execute the playbook. However, if the third-party tool does not integrate with Prism, then the administrator cannot use an alert trigger and has to use an event trigger instead.

References:

• Nutanix Calm User Guide: Chapter 8: X-Play
• Nutanix Calm DSL User Guide: Chapter 5: Playbooks
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide: Section 1: Describe and Differentiate Automation Concepts and Principles

The PagerDuty Integration service allows you to create and manage incidents in PagerDuty based on events in Nutanix X-Play. To configure the PagerDuty Integration service, you need to provide the following information:

• Service Name: The name of the PagerDuty service that you want to integrate with X-Play.
• API Key: The API key generated from the PagerDuty service settings.
• Plays: The plays that you want to trigger incidents in PagerDuty. You can select one or more plays from the list of available plays in X-Play. You can also specify the incident priority, escalation policy, and alert details for each play.
• Alert Grouping: (Optional) The alert grouping strategy that you want to use for the PagerDuty incidents. You can choose from the following options: