Nutanix NCP-MCA Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6 Exam Exam Practice Test

According to the Nutanix Multicloud Automation Administration (NMCAA) course1, one of the prerequisites for using X-Play to automate tasks on VMs is to have SSH enabled and configured on the target VMs. This allows X-Play to connect to the VMs and execute commands or scripts remotely. If the SSH service is not running on the VMs, then X-Play will fail to connect and perform the actions, resulting in the error message shown in the exhibit. The other options are not likely to cause this error, as they are either unrelated to X-Play (A and B) or not required for X-Play to work ©. References: Nutanix Multicloud Automation Administration (NMCAA) course

The best way to automate the scale-out of the application layer using a third-party tool is to create a Playbook with a webhook as a trigger and a REST API call as an action. A webhook is a mechanism that allows a third-party service to send a notification to a Calm server when a certain event occurs, such as a code commit or a build completion. A REST API call is a way to interact with the Calm server programmatically, such as launching a blueprint or scaling out a service. By creating a Playbook that combines these two elements, the administrator can enable the third-party tool to trigger the scale-out action on the Calm server with a single command. The other options are either not feasible, not efficient, or not relevant for this task. References: Nutanix Calm: Playbooks - Read the Docs and Nutanix Calm: REST API - Read the Docs.

 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.

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

To effectively automate the scaling of the environment, the administrator needs to know the steady state resource utilization and the expected resource utilization under load of the application, database, and web VMs. These two pieces of information will help the administrator to define the scaling policies, thresholds, and actions for the blueprint service that deploys the infrastructure. The administrator can use the Self-Service feature of Nutanix Multicloud Automation to create a blueprint service that can scale up or down based on the resource utilization metrics. The administrator can also use the Runbook feature to automate the scaling actions using scripts or APIs.

The other options are incorrect because:

• SLA uptime of the application: This is not a piece of information that is needed to automate the scaling of the environment. The SLA uptime of the application is a performance indicator that measures the availability and reliability of the application. The administrator can use the X-Play feature of Nutanix Multicloud Automation to create event-driven playbooks that can trigger actions based on alerts or schedules to ensure the SLA uptime of the application.
• If the application needs to be highly available: This is not a piece of information that is needed to automate the scaling of the environment. The high availability of the application is a design consideration that affects the architecture and configuration of the infrastructure and the application. The administrator can use the Projects feature of Nutanix Multicloud Automation to create projects that can define the availability domains, networks, and storage for the infrastructure and the application.

References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, Section 2.1, 2.2, 2.4, 2.5
• Nutanix Multicloud Automation Administration (NMCAA) Course, Module 2: Self-Service, Module 3: Runbook, Module 5: Projects
• Training Spotlight: Nutanix Multicloud Automation Administration (NMCAA), Video 2: Self-Service, Video 3: Runbook, Video 5: Projects

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”

 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

This solution meets the requirements of creating a multicloud, three-tier application using Calm. It ensures that each tier of the application has a redundant copy running on both Nutanix andAWS, and that the application can tolerate either a cloud provider outage or a local Nutanix cluster outage. The other options do not provide full redundancy for each tier, or require manual intervention to create the AWS instances. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 10; Nutanix Multicloud Automation Administration (NMCAA) Course, Module 5: Blueprints.

The hercules.log file is the log file for the Calm service, which is responsible for managing the integration with various cloud providers, including Azure. The administrator can check this log file to troubleshoot any issues related to the Azure integration, such as authentication, configuration, or communication errors. The other log files are not relevant for the Azure integration. The sytx.log file is the log file for the Sytx service, which is responsible for managing the Calm UI and API. The durga.log file is the log file for the Durga service, which is responsible for managing the Calm Marketplace and blueprints. The arjun.log file is the log file for the Arjun service, which is responsible for managing the Calm runbooks and playbooks.

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
• [Troubleshooting Calm | Nutanix Community]

 If a Blueprint deployment fails, the administrator can use the Continue option in the Self-Service Portal to resume the deployment from the point of failure. This option will retry the failed task and continue with the remaining tasks in the Blueprint. The administrator does not need to delete the application or launch a new one, as this would waste time and resources. Saving the Blueprint will not automatically retry the task, as the Blueprint is only a template for the deployment.

References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 3, Objective 3.1: Determine the causes of a Blueprint or Runbook deployment failure.
• Nutanix NCP-MCA Certification Exam Sample Questions, Question 17.

 In the context of Nutanix Multicloud Automation (NCP-MCA), the order of actions in a playbook is crucial for its successful execution. In this case, the playbook is designed to execute a script to fix a known problem in an application but keeps failing because it attempts to power off the VM and take a snapshot before executing the script. The correct order should be to execute the script first, then power off the VM if necessary, and finally take a snapshot. References: I found 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) 6.5 Exam: 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.
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide: This is another version of the exam blueprint guide that has similar content as the previous one.
• Free Questions for NCP-MCA by certscare - p2pexams.com: This is a PDF document that contains 11 questions and answers for the NCP-MCA exam. The question you asked is one of them, and the answer is the same as mine.

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 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

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

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.

 Nutanix Calm is a feature of Prism Central that enables you to automate the deployment and management of infrastructure and applications across multiple clouds. Prism Central is a centralized management plane that provides unified visibility and control over Nutanix clusters and services. Prism Element is the local management plane for each Nutanix cluster that runs the Acropolis Operating System (AOS). Both Prism Central and Prism Element are required for Nutanix Calm to function properly and access the resources and services of the Nutanix platform. References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 2 - Deploy and Configure Nutanix Calm and Related Components, page 1
• Nutanix Multicloud Automation Administration (NMCAA), Module 1 - Introduction to Nutanix Multicloud Automation, Lesson 1.1 - Nutanix Multicloud Automation Overview, page 4
• Nutanix Calm User Guide, Introduction to Nutanix Calm, Nutanix Calm Architecture

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

 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

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 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

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

The archived application logs within Prism Central can be found under Services > Calm > Settings. Calm automatically archives run logs of the deleted applications and custom actions that are older than three months. The administrator can download the archives within 7 days from the time of archive creation. For a running application, data is not archived for the system-generated Create actions. References: Nutanix Support & Insights

Nutanix Calm is a cloud-agnostic automation and orchestration solution that can be deployed on Nutanix AHV or any public cloud platform, such as AWS, Azure, or GCP. Calm can also manage applications across multiple cloud environments, including hybrid clouds. Calm cannot be deployed on vSphere Essential Edition or VMware ESXi, as these are not supported hypervisors for Calm. However, Calm can manage existing VMs on vSphere or ESXi clusters through the VMware provider. References:

• Nutanix Calm Configuration and Training1
• Nutanix Calm Admin and Operations Guide2

When configuring Playbooks to automate the scaling of CPU and memory resources for VMs, the administrator should consider the following prerequisites:

• CPU can be added to a powered on VM if the guest OS supports it. This is also known as hot-plug CPU. The administrator should check the compatibility of the guest OS and the hypervisor before enabling this feature. For example, Windows Server 2019 supports hot-plug CPU on AHV, ESXi, and Hyper-V, but not on XenServer1.
• Memory can be removed from a powered on VM if the guest OS supports it. This is also known as hot-unplug memory. The administrator should check the compatibility of the guest OS and the hypervisor before enabling this feature. For example, Linux supports hot-unplug memory on AHV, ESXi, and XenServer, but not on Hyper-V2.
• VM must be powered off to add CPU if the guest OS does not support hot-plug CPU. This is also known as cold-plug CPU. The administrator should plan for the downtime required to power off and power on the VM after adding CPU.
• VM must be powered off to reduce memory if the guest OS does not support hot-unplug memory. This is also known as cold-unplug memory. The administrator should plan for the downtime required to power off and power on the VM after reducing memory. References: Nutanix Multicloud Automation Administration (NMCAA), page 10; Nutanix Certified Professional - Multicloud Automation (NCP-MCA), section 3; Nutanix Support Portal - Guest OS Compatibility Matrix

A Prism Admin or Super Admin role can perform the following operations related to X-Play and Nutanix Calm12:

• Create, read, update, or delete an action template in the action gallery
• Create, read, update, delete, enable, and run playbooks
• Create, read, update, delete, enable, and run blueprints and runbooks
• Manage applications and projects
• Configure endpoints and plug-ins
• Access the library and categories Option A is incorrect because the action gallery does not support automation of action templates. Option C is incorrect because only a Prism Admin or Super Admin role can enable and run playbooks, not a Prism User role3. References:
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5
• Nutanix Multicloud Automation Administration (NMCAA)
• Prism user permissions – what are the options?

Calm can be deployed as a VM on ESXi or AHV hypervisors and leverage calm functionality without the Nutanix infrastructure. Calm can also be enabled inside of Prism Central, which is a VM that can run on any Nutanix supported hypervisor, including ESXi and AHV. However, Calm cannot be enabled inside of Prism Element, which is the management interface for each Nutanixcluster. Calm also cannot be deployed as a VM on Hyper-V, as this is not a supported hypervisor for Calm. References: Nutanix Calm Configuration and Training, Calm on ESXi Deployment | Nutanix Community, Nutanix Support & Insights

The administrator should modify the alert by adding the correct category and assign the category Environment:Development to development VMs. By doing this, they can filter out alerts for development VMs that are expected to have memory constrained alertsand focus on those that are critical, such as production VMs. This is based on the general practices in managing alerts in a multicloud environment, as well as the specific features and requirements of Nutanix Calm and Prism Central. References:

• How to create custom alert policies | Prism central | Nutanix Community
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5 Exam Blueprint Guide, Section 3: Validate Blueprints, Runbooks, Playbooks, and Automation Settings, Objective 3.1: Determine the causes of a Blueprint or Runbook deployment failure
• Nutanix Multicloud Automation Administration (NMCAA) course, Module 4: Nutanix Calm Governance, Lesson 1: Nutanix Calm Governance

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 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.

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

A Developer permission level grants access to create, update, delete, and duplicate blueprints in Nutanix Calm12. A Developer can also launch, manage, and delete applications from blueprints, as well as create, update, delete, and duplicate runbooks2. A Consumer can only launch and manage applications from blueprints, but cannot modify them2. An Operator can launch, manage, and delete applications from blueprints, as well as run and manage runbooks, but cannot create or modify them2. A Domain Admin can perform all the actions of a Developer and an Operator, as well as manage projects, categories, and endpoints2. References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5
• Nutanix Multicloud Automation Administration (NMCAA)

Runbooks are a feature of Calm that allows for the creation of task-based automation against dynamic lists of Windows or Linux VMs. A runbook is a collection of tasks that can be executed on one or more VMs or services. A task is a unit of automation that can perform actions such as executing commands, running scripts, invoking APIs, or sending notifications. A runbook can be triggered manually, on a schedule, or based on an event. Runbooks can be used to automate common operations such as backup, restore, patching, scaling, or troubleshooting. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 16; Nutanix Calm User Guide, section 3.4.

Playbooks are a collection of tasks that can be executed on demand or based on a trigger. There are two types of triggers available for executing Playbooks: manual and alert. A manual trigger allows you to run a Playbook on demand from the Prism Central UI or the Calm API. An alert trigger allows you to run a Playbook automatically when a specific alert is generated by Prism Central or a third-party system. Report and audit are not valid trigger types for Playbooks. References: Nutanix Multicloud Automation Administration (NMCAA), page 9; Nutanix Certified Professional - Multicloud Automation (NCP-MCA), section 1.

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 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

 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.