NCP-MCA Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6 Exam Questions and Answers

A Playbook action has a default memory limit of 256 MB, which can be increased up to 1024 MB in the advanced settings of the action. If the action requires more memory than the limit, it will fail with the error message “Internal Error, Maximum Memory size limit reached”. To resolve this issue, the administrator can edit the action and increase the memory limit to a suitable value, depending on the complexity and requirements of the action.

References:

• Nutanix Multicloud Automation Administration (NMCAA) Course, Module 3: X-Play, Lesson 3.3: Creating and Managing Playbooks, Slide 19: Action Settings
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, Section 3: Validate Blueprints, Playbooks, and Automation Settings, Objective 3.3: Determine the correct method to validate required Playbook configurations

When launching Calm blueprints, there are two view options available: Developer and Consumer. The Developer view allows you to create, edit, and manage blueprints, as well as access advanced features such as macros, actions, and scripts. The Consumer view allows you to launch and manage applications from the Marketplace, as well as access basic features such as variables, tasks, and alerts. The view option is determined by the role assigned to the user in the project. Users with the Project Admin or Project Auditor role can switch between the Developer and Consumer views, while users with the Project User role can only access the Consumer view. References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 1 - Describe and Differentiate Automation Concepts and Principles, page 3
• Nutanix Multicloud Automation Administration (NMCAA), Module 2 - Nutanix Calm, Lesson 2.1 - Nutanix Calm Overview, page 9
• Nutanix Calm User Guide, Introduction to Nutanix Calm, Nutanix Calm User Interface

The Audit tab of the Calm application shows the history of actions performed on the application, such as create, update, delete, launch, stop, etc. It also shows the status of the synchronization between Prism Central and Calm, which indicates if the changes made to the VMs on the AHV cluster are reflected in the Calm application. The administratorcan check the Audit tab to verify the changes and troubleshoot any issues with the synchronization. References:

• Nutanix NCP-MCA Certification Exam Sample Questions, Question 15
• Nutanix Certified Professional - Multicloud Automation, Page 17
• Nutanix Calm User Guide

According to the Nutanix Calm documentation1, the Snapshots tab allows the administrator to view, create, and restore snapshots of the VMs that are part of a blueprint. The Manage tab only shows the status and actions of the blueprint, and the Recovery tab is used for disaster recovery operations2. References:

• 1 Nutanix Calm: Introducing Snapshot and Restore Actions3
• 2 Nutanix Calm User Guide: Blueprint Operations

An X-Play Trigger is a condition that initiates a Playbook. There are four types of X-Play Triggers: Alert, Audit, Event, and Time1. An Alert Trigger is based on a Prism alert, such as a VM power state change or a disk failure. An Audit Trigger is based on a Prism audit entry, such as a user login or a cluster operation. An Event Trigger is based on a Prism event, such as a VM creation or deletion. A Time Trigger is based on a schedule, such as daily, weekly, or monthly2. In this scenario, the administrator needs to create a Playbook to be notified when VMs are deleted. Therefore, the appropriate X-Play Trigger would be an Event Trigger, since VM deletion is a Prism event. References: 1: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 42: Getting Started with Nutanix X-Play – Nutanix.dev

A post-create task is a task that runs after a blueprint or runbook deployment is completed. A post-create task can be used to perform additional configuration or automation on the deployed resources. An HTTP task is a task that executes an HTTP request to a specified URL, with optional headers, body, and authentication. An HTTP task can be used to trigger an API call to another system or service, such as creating a front end application. A predefined task is a task that uses a predefined script or command to perform a common operation, such as installing a package or running a service. A predefined task cannot be used to trigger an API call to another system or service. An eScript task is a task that executes a custom script written in JavaScript or Python. An eScript task can be used to perform complex logic or operations that are not available in predefined tasks. However, an eScript task requires more coding skills and testing than an HTTP task. A simple task is a task that executes a simple command or script on the target VM or host. A simple task cannot be used to trigger an API call to another system or service. References: 

https://www.nutanix.com/content/dam/nutanix/resources/support/ebg-ncp-mca-6.pdf

https://www.nutanix.com/support-services/training-certification/certifications/certification-details-nutanix-certified-professional-multicloud-automation-v6-5

The error “Connection refused” can occur due to several reasons but in the context of running a script through Calm on VM, it is most likely caused by firewall restrictions or insufficient permissions. Option A suggests that the VM port is not allowed by the firewall, meaning that the firewall settings are preventing the connection. This could be because specific ports needed for the script to run are being blocked. Option B indicates that the credentials have insufficient permissions, meaning that the user or system trying to execute the script does not have the necessary permissions to establish a connection. Option C is unlikely because the VM should be ready before the script is executed. Option D is possible but not specific enough to explain the connection issue. References: You can find more information about this topic in the following sources:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, Section 3 - Validate Blueprints, Runbooks, Playbooks, and Automation Settings, page 9
• Nutanix Multicloud Automation Administration (NMCAA), Module 5 - Troubleshooting, Lesson 1 - Troubleshooting Calm, page 5-4

 The Developer role is the most appropriate role for the end user who needs to modify the blueprints for the project. The Developer role allows the user to create, edit, and delete blueprints and runbooks within the project, as well as launch and manage applications from the Marketplace. The Developer role does not have the privileges to create or manage projects, users, roles, or categories, which are reserved for the Project Admin role. The Consumer role only allows the user to launch and manage applications from the Marketplace, but not to modify the blueprints or runbooks. The Operator role allows the user to monitor and manage the infrastructure and applications within the project, but not to create or edit the blueprints or runbooks.

References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 1 - Describe and Differentiate Automation Concepts and Principles, Objective 1.5 - Identify the capabilities of Projects
• Nutanix Multicloud Automation Administration (NMCAA), Module 3 - Self-Service Projects, Lesson 3.1 - Project Roles and Permissions

According to the Nutanix Calm Administration Guide1, the minimum system requirements for Prism Central are 32 GB of RAM and 8 vCPUs. If the production Prism Central has less than the minimum RAM, it may affect the performance of Calm and other services running on Prism Cen

 The Snapshot tab allows you to view the captured snapshots, restore applications from snapshots, and delete the snapshots for an application. Use this tab to create snapshots of single VM applications that are running with Nutanix as the provider1. You can also view the date and time, and the name of the snapshot, and perform actions like Delete, Clone, Restore2. The AMIS tab is for Amazon Machine Images, the Recovery point tab is for Calm applications, and the Manage tab is for day 2 actions3. References: Nutanix Support & Insights, List VMs with snapshots on Nutanix AHV, Nutanix Calm: Introducing Snapshot and Restore Actions

The error message “Authentication by failed” typically indicates an issue with the authentication credentials being used. Since the administrator is using SSH key-based credential to authenticate, it’s essential to ensure that the private key associated with this credential is correct and accessible. If there’s an issue with the private key, such as it being incorrect or inaccessible, authentication will fail. Increasing the retries or modifying the timeout will not help if the credential is invalid. Changing to password authentication credential may work, but it’s not the best option as it may compromise security and require additional configuration. References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 3 - Validate Blueprints, Runbooks, Playbooks, and Automation Settings, page 2
• Nutanix Multicloud Automation Administration (NMCAA), Module 5 - X-Play, Lesson 5.2 - Credential Management, page 7
• Nutanix Calm User Guide, Credential Management, SSH Key-Based Authentication

 In order to enable the developer to complete the requested task, AWS and Azure Providers need to be created (Option A). This is because, in the context of Nutanix Calm, providers are integrations with public and private cloud infrastructures. The developer is trying to deploy an application on AWS and Azure clouds but currently only has Nutanix as a configured provider. After creating the providers, they need to be added to the project (Option B) so that applications can be deployed on them. Option C is incorrect because environments are not required for multicloud deployments. Option D is also incorrect because Calm version 3.2.x is not relevant to the question.

References: The information can be verified from Nutanix official training and certification documents available at Nutanix Training & Certification. You can also check out the Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam guide for more details on the exam objectives and format. Additionally, you can watch the Nutanix Calm - Multicloud Automation playlist on YouTube for some video tutorials on Nutanix Calm features and functionalities.

Showback is a feature in Calm that allows administrators to track and report the costs of running applications and projects on different cloud platforms. Showback can be enabled in the Setting menu of Calm, under the Showback tab. There, the administrator can configure the cost models, cloud accounts, and currency for Showback. Showback can also be accessed from the Dashboard menu, where the administrator can view the cost reports and charts for different applications and projects. References: 

https://www.nutanix.com/support-services/training-certification/certifications/certification-details-nutanix-certified-professional-multicloud-automation-v6-5\

https://www.nutanix.com/content/dam/nutanix/resources/support/ebg-ncp-mca-6.pdf

To automate the creation of a new user in GitLab for every new development environment, the administrator should perform the following tasks within a Calm blueprint:

• Create an HTTP pre-create task to create the user in GitLab via REST API. This task will send an HTTP request to the GitLab server with the user information and credentials, and receive a response with the user ID and status. The administrator can use the response to verify the user creation and store the user ID as a variable for later use.
• Create runtime-editable variables for user and password in the blueprint. These variables will allow the administrator to specify the user name and password for the new GitLab user at the time of launching the blueprint. The variables can be passed as parameters to the HTTP pre-create task and used in the REST API call.
• The other two options are not correct because:
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam, page 17
• Nutanix Calm User Guide, section “HTTP Task”
• GitLab API Documentation, section “Create user”

To create a custom alert policy, the administrator needs to specify the entity type, the impact, the severity, the condition, and the notification method. In this case, the entity type is VM, the impact is performance, the severity is warning, the condition is CPU usage > 70%, and the notification method is email. Additionally, the administrator can use categories to filter the entities that are affected by the alert policy. By selecting the category Env:Production, the administrator can limit the alert policy to only apply to the production VMs.

References:

Nutanix

https://www.bing.com/th?id=OSK.rK3sz-kbZCnJ9cwhAmYELm3vDpqzAZFHBIZFgLsHbGQ &pid=cdx&w=128&h=128&c=7

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 2 - Deploy and Configure Self-service and Related Components, Objective 2.5 - Identify required configuration settings for a Self-Service deployment

• How to create custom alert policies | Prism central | Nutanix Community

When configuring Calm to use Kubernetes as a provider, the administrator can choose between two Kubernetes types: Karbon and Vanilla. Karbon is Nutanix’s own Kubernetes distribution that is integrated with Prism and AHV. Vanilla is any other Kubernetes distribution that is not Karbon, such as OpenShift, Rancher, or EKS. The administrator needs to provide the Kubernetes API endpoint and credentials for the Vanilla type, while the Karbon type is automatically discovered by Calm. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 14; Nutanix NCP-MCA Questions, question 102.

The error message “INTERNAL_ERROR: ErrorCode: 9” typically indicates an issue with the SSH service on the VMs. In this context, where a playbook is being executed to shut down Linux VMs, it’s essential that the SSH service is running to allow for remote management and execution of commands. If the SSH service isn’t running, the playbook won’t be able to execute commands on the VMs, leading to an internal error.

References:

• Nutanix Multicloud Automation Administration (NMCAA) Course, Module 3: X-Play, Lesson 3.3: Creating and Managing Playbooks, Slide 19: Action Settings
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, Section 3: Validate Blueprints, Playbooks, and Automation Settings, Objective 3.3: Determine the correct method to validate required Playbook configurations

UESTION NO: 80

An administrator is unable to launch a Calm blueprint (new and old). Launching an existing blueprint under this condition fails with the error message:

The project for this blueprint does not have any associated Nutanix account.

Downloading and uploading the new blueprint also fails with

Launch with Variables' Profile expected to fall as Windows Server VWs attached with deleted Account.

Please modify them to use different account and try again.

Why is the administrator seeing this issue?

A. The account is in a failed state.

B. The has not been created.

C. The account is not verified.

D. The account been deleted.

Answer: D

The error messages indicate that the blueprint is trying to use a Nutanix account that no longer exists. This could happen if the account was deleted by another administrator or by a playbook action. The administrator should check the project settings and verify that the Nutanix account is still available and associated with the project. If not, the administrator should create a new account or use an existing one and update the blueprint accordingly. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam Blueprint Guide, page 9; Nutanix Certified Professional - Multicloud Automation (NCP-MCA), section 3; Nutanix NCP-MCA Certification Exam Sample Questions, question 80.

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 Task Library is a centralized repository of tasks that can be reused across multiple blueprints. The administrator can publish a task to the Task Library by clicking on the Publish icon in the task editor. The task will then be available in the Task Library tab under the Tasks section in the Calm UI. The administrator can select the task from the TaskLibrary and drag and drop it into another blueprint. This way, the administrator can reuse the task with the least amount of effort.

References:

• Nutanix Certified Professional Multicloud Automation (NCP-MCA) 6 Exam, page 11
• Nutanix University - NCP-MCA 6 Exam Prep - Tasks and Task Library

A provider is a configuration that allows Nutanix Calm to interact with a public cloud platform, such as AWS, Azure, or GCP. A provider contains the credentials, settings, and policies required to deploy and manage VMs on the public cloud. Before creating a blueprint for a new public cloud environment, the administrator should create a new provider for AWS and specify the region, access key, secret key, and other parameters. This will enable the administrator to select the AWS provider as the deployment location for the blueprint and configure the VM attributes accordingly. References: Nutanix Multicloud Automation Administration (NMCAA), page 15; Nutanix Certified Professional - Multicloud Automation (NCP-MCA), section 2.

Alerts are a way of monitoring the health and performance of the Nutanix cluster and the VMs running on it. Alerts can be triggered by various metrics, such as CPU usage, memory usage, disk space, network traffic, etc. Alerts can also be configured to send notifications to the administrator or other recipients via email, Slack, PagerDuty, etc. To satisfy the request from the Accounting department, the administrator should create an Alert with the following settings:

• Trigger: CPU Usage (%) > 90 OR Memory Usage (%) > 90
• Scope: VM
• Category: LOB:Accounting
• Notification: Email to accounting@company.com This way, the Alert will only apply to the VMs that belong to the Accounting department, and will send an email notification to the Accounting department when any of their VMs exceed the specified thresholds. References: Nutanix Multicloud Automation Administration (NMCAA), page 9; Nutanix Certified Professional - Multicloud Automation (NCP-MCA), section 1; [Nutanix Prism Central Guide - Alerts]

An event trigger is a type of trigger that can be used to execute a playbook when a specific event occurs in the Nutanix platform. An event trigger can be configured with various parameters, such as the event type, the target VM, the target VM category, the target project, and the target user. In this scenario, the administrator wants to be notified when a subset of VMs within the Environment:Dev category is restored from snapshot. Therefore, the event trigger should have the following parameters:

• Event type: Snapshot Restoration. This is the event that indicates a VM has been restored from a snapshot.
• Target VM: VMS in Environment: Dev. This is the filter that specifies which VMs are relevant for the trigger. By selecting VMS in Environment: Dev, the trigger will only apply to the VMs that belong to the Environment:Dev category.
• Other parameters: These can be left as default or customized as needed.

References:

• Nutanix Multicloud Automation Administration (NMCAA) Course, Module 3: X-Play, Lesson 3.2: Creating and Managing Playbooks, Slide 13: Event Trigger
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, Section 3: Validate Blueprints, Playbooks, and Automation Settings, Objective 3.1: Determine the causes of a Playbook execution failure

Nutanix Calm supports various providers to manage and orchestrate applications across different cloud environments. Providers are the cloud platforms or services that host the VMs or containers that run the application components. Calm supports the following providers12:

• Nutanix AHV
• VMware vSphere
• AWS
• Azure
• GCP
• Kubernetes
• Bare Metal
• OpenStack
• Cloud-Init
• Terraform

Among the options given, only Kubernetes and GCP are supported providers in Calm. Oracle Cloud and IBM Cloud are not supported providers in Calm. References:

• 1: Nutanix Calm Admin and Operations Guide3
• 2: Nutanix Calm Configuration and Training4

Scaling VM replica settings allow you to specify the minimum, maximum, and default number of VMs that can be created from a blueprint service. The minimum and default values must be equal to or greater than the number of VMs needed at any time and at time of deployment, which is 2 in this case. The maximum value must be equal to or less than the project quota divided by the VM resources, which is 100/12 = 8 for vCPUs and 300/24 = 12 for memory. The lowest of these two values is the limit for the maximum value, which is 8. Therefore, the only option that meets all the requirements is B. MIN: 2, MAX: 7, Default: 2.

References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 10, Objective 3.1: Given a scenario, create a blueprint to deploy infrastructure and applications using Self-Service
• Nutanix Multicloud Automation Administration (NMCAA), Module 5: Self-Service, Lesson 5.2: Blueprint Design, slide 23: Scaling VM Replica Settings
• Nutanix Certified Professional Multicloud Automation (NCP-MCA) 6 Exam, page 10, Objective 3.1: Given a scenario, create a blueprint to deploy infrastructure and applications using Self-Service

The policy engine is a single VM setup for the single or scale-out Prism Central. When you enable the policy engine for your Calm instance, a new VM is created and deployed for the policy engine. All you need is an available IP address that belongs to the same network as that of your Prism Central VM for the policy engine VM. You do not need to provide any public or private keys, or any Prism Central virtual IP addresses for this task. References: Nutanix Support & Insights, Calm on ESXi Deployment | Nutanix Community

The error message indicates that the script failed to authenticate to the remote server using CredSSP. CredSSP is a security mechanism that allows a client to delegate its credentials to a remote server for authentication. To use CredSSP, both the client and the server need to enable it and configure the role and the trusted hosts. The command Enable-WSManCredSSP -Role Client enables CredSSP on the client side and specifies the remote server as a trusted host. This command should be added to the script before invoking the Invoke-Command cmdlet that runs the script block on the remote server. The other commands are either irrelevant or incorrect for this scenario. References: Nutanix Calm: PowerShell Scripts - Read the Docs and Enable-WSManCredSSP (Microsoft.PowerShell.Management) - PowerShell | Microsoft Docs.

https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Calm-Admin-Operations-Guide-v3_6_2:nuc-macros-variables-overview-c.html

 The alert in Prism Central indicates that Calm showback is not able to reach the beam service. This could be due to network connectivity issues or incorrect configurations. The administrator should check the DNS configuration in Prism Central (Option A) to ensure that it is correctly configured to allow communication with the Beam service. Additionally, checking if Prism Element is configured with Proxy settings (Option C) is essential as it can also affect the communication between Calm and Beam. Pulse (Option B) and Flow (Option D) are not related to the Calm showback feature and do not impact its functionality.

References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 2 - Deploy and Configure Nutanix Calm and Related Components, Objective 2.4 - Identify required configuration settings for a Nutanix Calm deployment
• Enabling and Disabling Showback in Calm | Nutanix Community

The most likely reason for this behavior is that the developer created a post-create task for reserving the IP address. A post-create task is executed after the VM is created and powered on, which means that the VM already obtained a DHCP IP address before the task is run. To reserve the IP address in IPAM as part of the deployment process, the developer should create a pre-create task instead. A pre-create task is executed before the VM is created and powered on, which allows the task to reserve the IP address in IPAM and assign it to the VM. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 15; Nutanix NCP-MCA Questions, question 57.

A Branch Condition is a type of action in X-Play that allows you to create conditional logic based on the output of a previous action or a custom expression. A Branch Condition can have multiple branches, each with a different condition and a different set of actions to execute if the condition is met. The minimum number of actions required in a Branch Condition is two: one for the condition itself, and one for the action to perform if the condition is true. If the condition is false, the Branch Condition will skip to the next action in the Playbook. You can add more branches to a Branch Condition, but you cannot have less than two. References: Nutanix Calm: Playbooks - Read the Docs and Nutanix Calm: Branch Condition - Read the Docs.

When a Blueprint is launched via Marketplace, it uses the credential that is configured in the Project Environment. If the credential is invalid, the Blueprint deployment will fail with a check login error. To fix this issue, the developer needs to verify and update the credential in the Project Environment and ensure that it has the required permissions to access the target infrastructure and applications. References: Nutanix Multicloud Automation Administration (NMCAA), page 29-30; [Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide] (https://www.nutanix.com/content/dam/nutanix/resources/support/ncp-mca-ebg.pdf), section 3.1.

Scaling VM replica settings allow you to specify the minimum, maximum, and default number of VMs that can be created from a blueprint service. The minimum and default values must be equal to or greater than the number of VMs needed at any time and at time of deployment, which is 2 in this case. The maximum value must be equal to or less than the project quota divided by the VM resources, which is 100/12 = 8 for vCPUs and 300/24 = 12 for memory. The lowest of these two values is the limit for the maximum value, which is 8. Therefore, the only option that meets all the requirements is B. MIN: 2, MAX: 7, Default: 2.

References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 10, Objective 3.1: Given a scenario, create a blueprint to deploy infrastructure and applications using Self-Service
• Nutanix Multicloud Automation Administration (NMCAA), Module 5: Self-Service, Lesson 5.2: Blueprint Design, slide 23: Scaling VM Replica Settings
• Nutanix Certified Professional Multicloud Automation (NCP-MCA) 6 Exam, page 10, Objective 3.1: Given a scenario, create a blueprint to deploy infrastructure and applications using Self-Service

The port 5986 is used for PowerShell Remoting over HTTPS, which is a secure way of executing PowerShell commands on a remote Windows VM. Calm uses PowerShell Remoting to run scripts on Windows VMs as part of the blueprint actions. Therefore, the port 5986 needs to be opened on the VM firewall to allow the communication between Calm and the VM. The other ports are not related to PowerShell Remoting, as they are used for SQL Server (1433), Remote Desktop Protocol (3389), and PowerShell Remoting over HTTP (5985). References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam Blueprint Guide, page 10; Nutanix Certified Professional - Multicloud Automation (NCP-MCA), section 3; Nutanix Calm User Guide,page 93.

The error message indicates that the password parameter is not a secret parameter, which means it is not encrypted and stored securely in the Calm database. This can happen when a Playbook is cloned from another Playbook that has a password parameter defined as a secret parameter. The cloned Playbook will inherit the password value from the original Playbook, but it will not be a secret parameter. To resolve this issue, the administrator needs to either delete the password parameter and create a new one as a secret parameter, or edit the password parameter and mark it as a secret parameter. References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 15, section 4.2.1
• Nutanix Calm Playbooks
• Nutanix Calm Parameters