NCP-MCA Exam Results

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 image is unavailable for deployment on the cluster because the cluster and the image do not have the proper categories assigned for the placement policy. A placement policy is a set of rules that determines which clusters and images are available for VM deployment based on the categories and values assigned to them. If the cluster and the image do not match the placement policy criteria, they will not be shown as options for VM deployment. Therefore, the administrator needs to assign the appropriate categories and values to the cluster and the image to make them compatible with the placement policy. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 12; Nutanix NCP-MCA Questions, question 111.

Categories are a way of organizing and managing resources in Nutanix Calm. Categories can be used to define access policies, filter resources, and group applications. By creating and assigning the Linux OS Category to the newly-created VM, the administrator can grant access to the OS Team based on their Active Directory Group membership. The OS Team can then use the web SSH console to access the Linux VM from the Calm UI.

References:

Nutanix Support & Insights, section “Categories”

Nutanix Support & Insights, section “Accessing the Web SSH Console”