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

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

The Policy Engine is a Calm feature that allows you to define and enforce policies for your projects, such as quotas, approvals, and actions. You can use the Policy Engine to set project quotas for the ESXi hypervisor, such as the number of VMs, CPU cores, memory, and storage that can be provisioned by the project. This helps you to control the resource consumption and allocation of your ESXi clusters. References:

• Nutanix Support & Insights: This is the official Nutanix documentation for Calm on ESXi, where you can find information about the Policy Engine and how to configure it for your projects.
• Nutanix Exam NCP-MCA Topic 2 Question 28 Discussion: This is a forum where you can find discussions and explanations for Nutanix certification exam questions, including question 28 from topic 2, which is similar to your question.
• Calm on ESXi Deployment: This is a Nutanix community post where you can learn more about how to deploy and use Calm on ESXi.

To deploy blueprints to Calm SaaS and execute them, the administrator must first configure a site-to-site VPN tunnel and a tunnel entity in the environment where the blueprint will be deployed. A site-to-site VPN tunnel is a secure connection between two networks over the internet that allows Calm SaaS to communicate with the on-premises or cloud environment. A tunnel entity is a logical representation of the VPN tunnel in Calm SaaS that contains the tunnel configuration and credentials. The administrator must also register the environment and the provider accounts in Calm SaaS before deploying the blueprints. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 9; Nutanix Calm SaaS User Guide, section 3.1.1 and 3.1.2.

Calm Runbooks are a way to automate workflows that span across multiple applications, services, or platforms. They can be used to perform actions such as provisioning, scaling, backup, restore, etc. Calm Runbooks can be added to the Library and reused in different Blueprints or Projects. A Post VM Delete Task is a special type of Task that is executed after a VM is deleted from a Blueprint. By creating Calm Runbooks for each of the manual steps required to decommission a VM, and adding them to the Library, the administrator can simplify the VM Decommission Process by consuming them inside of a Post VM Delete Task. This way, the application owners only need to delete the application from the Calm project, and the rest of the steps will be automated by the Runbooks. References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 16, section 4.3.1
• Nutanix Calm Runbooks
• Nutanix Calm Library
• Nutanix Calm Tasks

Calm integrates natively with AWS and AHV as providers. A provider is a cloud platform or infrastructure that hosts the application VMs or services. Calm supports various providers such as Nutanix, AWS, Azure, GCP, VMware, and Kubernetes. AWS and AHV are two of the most commonly used providers in Calm, as they offer scalability, flexibility, and cost-efficiency for deploying applications. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 11; Nutanix Calm User Guide, section 3.1.

The Restart Action of a Service allows the developer to define custom tasks that will be executed when the service is restarted. An Execute Task can run any script or command on the target VM, such as restarting the IIS service. This way, the Operator can use the Self-Service Portal to restart the service without logging into the VM or using another tool.

References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 2, Objective 2.1: Given a scenario, create a blueprint to deploy infrastructure and applications using Self-Service.
• Nutanix Certified Professional Multicloud Automation (NCP-MCA) 6 Exam, Page 11, Section 2, Objective 2.1: Given a scenario, create a blueprint to deploy infrastructure and applications using Self-Service.

 A macro is a placeholder for a value that is resolved at runtime. Macros can be used to reference various Calm objects, such as variables, secrets, credentials, tasks, and services. The correct syntax for using a macro within a Calm blueprint is @@{calm.object}(@@, where calm.object is the name of the object to be referenced. For example, @@{username}(@@ would resolve to the value of the username variable at runtime. The other options are incorrect syntaxes for macros and would not be resolved by Calm. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6 Exam, Nutanix Certified Professional - Multicloud Automation

Nutanix provides a documented process to seed Github based scripts into the Calm Task Library, which allows users to import and use custom tasks from the Nutanix public Github repository or any other Github repository. This process is described in the Nutanix Calm DSL User Guide and the Nutanix Calm DSL Tutorial.

Nutanix also publishes official vetted blueprints and tasks to Nutanix’s public Github Calm repository, which is located at https://github.com/nutanix/blueprints . These blueprints and tasks are created and maintained by Nutanix engineers and can be used as reference or templates for building Calm applications. Some examples of these blueprints and tasks are:

• Kubernetes Cluster: A blueprint that deploys a Kubernetes cluster on Nutanix AHV using Calm.
• MySQL HA: A blueprint that deploys a MySQL cluster with high availability on Nutanix AHV using Calm.
• Windows Server: A blueprint that deploys a Windows Server 2019 VM on Nutanix AHV using Calm.
• [Install Python]: A task that installs Python on a Linux VM using Calm.

Calm’s public repository does not contain Nutanix-vetted custom scripts created and published by community members. These scripts are hosted in a separate repository called [Automation], which is a centralized repo for community driven Nutanix automation. These scripts are not officially supported or endorsed by Nutanix and may not be compatible with the latest versions of Calm or Nutanix products.

Nutanix does not provide documented processes to seed scripts from any source repository. Users can only import scripts from Github repositories using the Calm Task Library. Other source repositories are not supported by Calm.

References:

• Nutanix Calm DSL User Guide
• Nutanix Calm DSL Tutorial
• Nutanix Calm Blueprints
• Kubernetes Cluster
• MySQL HA
• Windows Server
• [Install Python]
• [Automation]

 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 easiest way to satisfy the request is to add an Email action to the end of the existing playbook and use the {{action[index] .stdout}} parameter in the Message field. This way, the administrator does not need to modify the script or create a file to store the output. The {{action[index] .stdout}} parameter will capture the standard output of the previous action, which is the VM SSH action that executes the script. The Email action will then send the output as the message body to the specified recipients. 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 10
• Nutanix Multicloud Automation Administration (NMCAA), Module 4 - X-Play, Lesson 2 - Playbooks, page 4-11

According to the Nutanix Calm documentation1, to scale out an existing Calm environment, the administrator needs to back up the data and create three Calm VMs from the Calm VM OVA template. The administrator then needs to configure the Calm VMs as a cluster and restore the data from the backup. The other options are incorrect because they either do not use the correct image format, do not create a cluster of Calm VMs, or destroy the existing Calm VM. References:

• 1 Nutanix Calm User Guide: Scaling Out the Calm Cluster2

The error message in the exhibit indicates a mismatch between the number of network settings and the number of NICs on the VM. This is a common validation error when saving Calm Blueprints for VMware, where it is essential to ensure that these configurations match to avoid issues with VM deployment and operation1. References: 1: Nutanix NCP-MCA Certification Exam Sample Questions2

The most optimal way to correct the failed deployment is to retry the failed deployment. This option allows the administrator to resume the deployment from the point of failure, without having to redeploy the entire application or create a new runbook. Retrying the failed deployment also preserves the application state and configuration, and avoids creating duplicate resources or conflicts.

Redeploying the application is not the best option, because it requires the administrator to delete the existing application and launch a new one from scratch. This option wastes time and resources, and may result in data loss or inconsistency.

Creating a runbook to retry is also not the best option, because it requires the administrator to write a custom script or workflow to handle the retry logic. This option adds complexity and overhead to the automation process, and may not be compatible with the original blueprint or application.

Rewriting the blueprint to have error handling is a valid option, but it is not the most optimal one. This option requires the administrator to modify the blueprint code and add logic to handle different types of errors and exceptions. This option improves the robustness and reliability of the blueprint, but it does not correct the failed deployment itself. The administrator still has to redeploy the application or retry the failed deployment after rewriting the blueprint.

References:

• Nutanix Calm User Guide: Chapter 6: Managing Applications
• Nutanix Calm DSL User Guide: Chapter 4: Blueprints
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide: Section 3: Validate Blueprints, Runbooks, Playbooks, and Automation Settings

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

To enable Calm, the administrator needs to log on to Prism Central with a local ADMIN account and click Services -> Calm -> Enable. This will install the Calm service on Prism Central and allow the administrator to access the Calm UI and features. The other options are incorrect because they either refer to Prism Element, which is not the correct platform for Calm, or they involve unnecessary or incorrect steps. References: [Enabling and Accessing Calm | Nutanix Community] (https://next.nutanix.com/installation-configuration-23/enabling-and-accessing-calm-40191); [Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide] (https://www.nutanix.com/content/dam/nutanix/resources/support/ds-ncp-mca.pdf), section 2.1.

The administrator should assign the VMs to an Inactive:VM category as an action and trigger a playbook on alert with the Inactive VM alert policy. By doing this, they can create a custom category to group and identify the inactive VMs and use a custom alert policy to trigger a playbook that can perform automated actions on them, such as powering them off, deleting them, or sending notifications. This is based on the general practices in managing VMs in a multicloud environment, as well as the specific features and requirements of Nutanix X-Play and Nutanix Calm. References:

• How to create custom categories | Prism central | Nutanix Community
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5 Exam Blueprint Guide, Section 1: Describe and Differentiate Automation Concepts and Principles, Objective 1.4: List how to implement categories for the appropriate use cases
• Nutanix Multicloud Automation Administration (NMCAA) course, Module 3: Nutanix X-Play, Lesson 2: Nutanix X-Play Playbooks
• Nutanix Multicloud Automation Administration (NMCAA) course, Module 4: Nutanix Calm Governance, Lesson 2: Nutanix Calm Alerts

The easiest way to automate the VM utilization and resource allocation is to use a playbook that has been already tested and validated in a test environment. A playbook is a collection of actions that can be triggered by events or schedules to perform various tasks on the Nutanix platform. By importing the playbook from the test environment to the production environment, the administrator can save time and effort in creating anew playbook from scratch. The administrator only needs to adjust the values of the playbook parameters, such as the VM name, the CPU and memory thresholds, the VCPU and memory increments, and the notification settings, to match the production environment. The playbook can then be executed manually or automatically based on the desired frequency and conditions.

References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 3 - Validate Blueprints, Runbooks, Playbooks, and Automation Settings, Objective 3.3 - Determine the correct method to validate required Playbook configurations
• Nutanix Multicloud Automation Administration (NMCAA), Module 4 - X-Play, Lesson 4.2 - Playbooks
• How to create and execute playbooks in Prism Central | Nutanix Community

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

To make a Blueprint visible to a specific Project, it needs to be approved and published with that Project. This ensures that only authorized Blueprints are available for consumption by the Project members. Applying a Category or a version number to the Blueprint does not affect its visibility to the Project. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 14, section 3.1.2

The Playbook is designed to manually reduce the vCPU count on any selected VM within the environment. However, it failed during a test run on VM2 because there was a running snapshot of the VM. According to Nutanix Multicloud Automation (NCP-MCA) principles, you cannot reduce the vCPU count on a VM that has an active snapshot1. This is because the snapshot captures the state of the VM configuration and data, and reverting to a snapshot will restore both the guest OS and the virtual hardware2. Therefore, changing the vCPU count while a snapshot is running will cause inconsistency and error. The other options are incorrect because:

• A. The Playbook can be executed against a VM on AHV, as long as there is no snapshot running3.
• B. The VM does not need to be powered off before vCPU can be reduced, as this can be done using hot-plug CPU feature4.
• D. The play will not cause the VM to go below the minimum vCPU, as the minimum number of vCPUs is set to 1 in the Playbook, and the VM has 4 vCPUs initially. References: Nutanix Support & Insights, Solved: Snapshot query !! - VMware Technology Network VMTN, Calm on ESXi Deployment | Nutanix Community, Virtual CPU Configuration and Limitations - VMware Docs

 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

The Calm Marketplace acts as an application store, providing end users with a catalog of available applications. By default, Calm comes pre-seeded with validated Blueprints for multiple open source and enterprise applications. These are the set of pre-seeded application Blueprints. Additionally, Marketplace Manager acts as a staging area for publishing default and user-created Blueprints to your local Marketplace. These are the published and versioned Blueprints. The other two options, library of executable tasks and store of all Blueprints created in Calm, are not features of the Calm Marketplace. References: Calm: Marketplace - Read the Docs and Calm: Marketplace - Read the Docs

The Calm SaaS API key consists of two components: name and token. The name component is analogous to the ID or username you provide when you configure your Calm tunnel client VM to establish the tunnel connection. The token component is analogous to the password portion of the HTTP basic authentication. The Calm SaaS API key is used along with the Calm APIs and Calm DSL to access Calm. The API key file that you download will have the name and token components in the JSON format. References: Nutanix Support & Insights

In the context of deploying an application with Calm, if a customer receives an error for a Linux VM, it could be due to the absence of network adapters selected for the Address box in the Connection section within the blueprint. This means that there is no specified network connection for the VM, leading to a failure in script execution. References: Ifound some references from Nutanix Multicloud Automation (NCP-MCA) Learning documents or resources that might be helpful for you:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide: This is the official exam blueprint guide that covers the objectives, topics, and skills required for the certification. It also provides some sample questions and answers. The question you asked is similar to the one in section 3.1.1.
• Nutanix Multicloud Automation Administration (NMCAA): This is a training course that teaches you the skills needed to install, configure, operate, and manage Nutanix X-Play and Nutanix Calm. It includes topics such as blueprint creation, connection configuration, and script execution.
• Nutanix Calm User Guide: This is a user guide that explains how to use Nutanix Calm to automate the deployment and management of applications across different environments. It includes topics such as connection settings, blueprint validation, and error handling.

 To view the last two actions taken by a single VM blueprint, the administrator should go to the History Tab. This tab shows the history of all the actions performed on the blueprint, such as launch, update, delete, etc. The administrator can filter the history by date, action, status, and user. The history tab also provides details of each action, such as the start time, end time, duration, and logs.

• The other three options are not correct because:
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam, page 18
• Nutanix Calm User Guide, section “Blueprint History”

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 conditional playbook and create a playbook using alert to accomplish this task. A conditional playbook is a type of playbook that allows the administrator to define different actions based on certain conditions or criteria1. A playbook using alert is a type of playbook that is triggered by an alert policy that monitors the VM status2. By using these two features, the administrator can create a playbook that checks if the rebooted VM is the mission-critical VM and sends a notification to the on-call administrator, or else sends an email to the Operations team.

References:

• Nutanix Multicloud Automation Administration (NMCAA) course, Module 3: Nutanix X-Play, Lesson 2: Nutanix X-Play Playbooks, Topic: Conditional Playbooks
• Nutanix Multicloud Automation Administration (NMCAA) course, Module 4: Nutanix Calm Governance, Lesson 2: Nutanix Calm Alerts, Topic: Alert Policies and Playbooks
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5 Exam Blueprint Guide, Section 1: Describe and Differentiate Automation Concepts and Principles, Objective 1.3: Define the components of X-Play

 A variable is a placeholder for a value that can be used in a blueprint or a script. A variable can be defined at the global, project, or blueprint level. A global variable is available to all projectsand blueprints, while a project variable is available to all blueprints within a project, and a blueprint variable is available only to the blueprint where it is defined. To make a variable visible to a blueprint, the developer needs to share the variable with the project that contains the blueprint. This can be done by going to the Variables page in the Calm UI and clicking on the Share button next to the variable name. Then, the developer needs to select the project from the drop-down list and click on Save. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 14; Nutanix Calm User Guide, section 3.2.

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

Protection Domains are a Nutanix feature that allows you to replicate data across clusters or to a remote site. You can use Protection Domains to replicate images from one cluster to another, and then use them for workload automation. This is one of the methods documented in the Nutanix Solutions Portal for Citrix MCS on Nutanix AHV1. Alternatively, you can also use Prism Central to manage multiple clusters and use Protection Policies to replicate images across clusters2. However, this option is not listed in the question, so the best answer is A. References:

• 1: Multi Cluster Image Replication for Citrix MCS on Nutanix
• 2: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide

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

 A Playbook is a set of actions that are triggered by an event or a schedule. To run a Playbook, it must be enabled first. If a Playbook is not enabled, it will not respond to any events or schedules, and no Plays will be recorded for it. Therefore, the most likely cause of the issue is that the administrator forgot to enable the Playbook after building it. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 13, section 3.2. Nutanix Multicloud Automation Administration (NMCAA) course, module 4, lesson 2.

 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.