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 a new 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 error code 1314 indicates that the user does not have the required privilege to perform the requested operation. This means that the credentials provided in the Calm Blueprint are not valid or do not have enough permissions to run the script on the Windows machine. To fix this issue, the administrator should verify the credentials and ensure that they have the appropriate rights to execute the script, such as local administrator or domain administrator privileges. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 15, section 3.3. Nutanix Multicloud Automation Administration (NMCAA) course, module 5, lesson 2. Nutanix NCP-MCA Certification Exam Sample Questions, question 25

After upgrading Self-Service (formerly Calm) from version 3.3 to 3.6, the administrator noticed that Policy Engine scheduled jobs were failing and an alert was being presented in Prism Central. This issue is likely due to a version mismatch between the upgraded components. The recommended solution is to use Lifecycle Manager (LCM) to upgrade the Policy Engine to ensure compatibility with the new version of Self-Service.

References:

Nutanix documentation on Upgrading Components with LCM.

Nutanix Best Practices for Managing Upgrades.

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 and AWS, 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.

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

 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.

The error message indicates that customization of the guest operating system is not supported. This issue often arises because open-vm-tools is not installed or not running on the Redhat Enterprise Linux VM. open-vm-tools is necessary for vSphere to perform guest customization tasks, such as setting the hostname, IP configuration, and other initialization tasks.

References:

Nutanix documentation on Guest Customization Requirements.

VMware documentation on Installing Open VM Tools.

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

When a play is stuck in a suspended state, a common reason is that the playbook was set with a Manual trigger and requires manual intervention to proceed. This can occur if the playbook is designed to pause at a certain step, waiting for an administrator or user to manually approve or provide additional input before continuing.

References:

Nutanix documentation on Playbook Triggers.

Nutanix Best Practices for Playbook Automation.

Autopilot is a feature of Nutanix Calm that allows the administrator to automate the execution of playbooks based on predefined conditions or triggers. Autopilot can optimize the performance, availability, and cost of applications by applying the appropriate actions in response to events or metrics. Before configuring autopilot, the administrator must be aware of the following limitations12:

Autopilot never waits for approvals. This means that the administrator must ensure that the playbooks are tested and verified before enabling autopilot. Autopilot will execute the playbooks without any human intervention or confirmation.

Autopilot feature only applies to metric-based alerts as triggers. This means that the administrator can only use metrics from the Nutanix Prism Central or the Nutanix Karbon clusters as the conditions for triggering the playbooks. Autopilot does not support other types of triggers such as schedules, webhooks, or manual triggers. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 10; Nutanix Calm SaaS User Guide, section 4.3.

The Plays dashboard in Prism Central provides a centralized view of all the Playbooks that have been executed across the clusters registered with Prism Central. It shows the status, duration, and output of each Playbook run, as well as the details of the triggers, targets, and actions involved. An administrator can use the Plays dashboard to troubleshoot why a Playbook failed to grow the memory of a VM by checking the error messages, logs, and output of the Playbook run. The other options are not the correct places to check for Playbook failures, as they do not provide the same level of information and visibility as the Plays dashboard. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6 Exam, Nutanix Exam NCP-MCA Topic 4 Question 20 Discussion

In Nutanix Calm, the RBAC (Role-Based Access Control) role that enables adding VMs to a project is the Project Admin role. Project Admins have the necessary permissions to manage and configure resources within a project, including the addition of VMs, handling project settings, and managing application blueprints.

References:

Nutanix Calm documentation on RBAC Roles.

Nutanix Best Practices for Project Administration.

An administrator can look to view a list of executed playbooks in two locations: Executions and Plays. The Executions page shows the status and details of all the playbooks that have been executed across all the projects. The Plays page shows the status and details of all the playbooks that have been executed within a specific project. The Lists page shows the predefined and custom lists that can be used as inputs for playbooks. The Dashboard page shows the overview and statistics of the X-Play service. References:

Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 3 - Validate Blueprints, Runbooks, Playbooks, and Automation Settings, page 4

Nutanix Multicloud Automation Administration (NMCAA), Module 5 - X-Play, Lesson 5.3 - Playbook Management, page 2

Nutanix Calm User Guide, X-Play, Executions

The warnings in the exhibit indicate that certain variables are missing or incorrectly defined. To resolve these warnings, the administrator should:

Create the variable under the action: Ensure that the necessary variables are defined in the scope of the action where they are required.

Create an add_worker_node_count variable: Specifically, the blueprint requires a variable named add_worker_node_count. This variable should be defined and given an appropriate value to ensure the action can execute properly.

References:

Nutanix Calm documentation on Blueprint Variables.

Nutanix Best Practices for Blueprint Development.

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.

In Nutanix, Categories can be assigned to various entities to help organize and manage resources. The two entities that can be assigned categories are:

Hosts: Categories can be used to tag and manage hosts within the infrastructure.

VMs: Categories can also be assigned to virtual machines, allowing for better organization and management based on specific attributes or requirements.

References:

Nutanix documentation on Category Management.

Nutanix Best Practices for Using Categories.

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

To run a resource-intensive script on separate test environments at different times, the administrator should publish a Runbook. Runbooks allow for the automation of tasks across multiple environments and can be scheduled to run at specific times. Additionally, they can be modified by the development team as needed to adapt to changes in the script.

References:

Nutanix Calm documentation on Runbook Publishing.

Nutanix Best Practices for Automation and Scheduling.

To ensure that checks can be implemented in a single task while creating an application using NDB (Nutanix Database Service), the administrator should run an eScript task. eScript tasks allow for more complex scripting and logic to be executed, including performing checks, handling conditions, and interacting with APIs.

References:

Nutanix Calm documentation on eScript Tasks.

Nutanix Best Practices for Automating Database Management.

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]

 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

To automate routine tasks such as acknowledging alerts, generating reports, and looking up cluster details on a set interval, the administrator should implement a Time Trigger. Time Triggers allow actions to be scheduled to run at specific times or intervals, ensuring consistent execution without manual intervention.

References:

Nutanix Calm documentation on Triggers.

Nutanix Best Practices for Automating Routine Tasks.

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

The options for adding pre-create tasks and installing packages in the VM are grayed out because there are no credentials added yet. Nutanix Calm requires VM credentials to perform package installations and pre/post tasks, as these actions need access to the VM to execute the necessary commands and scripts.

References:

Nutanix Calm documentation on Managing VM Credentials.

Nutanix Best Practices for Blueprint Configuration.

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

Substrates are the components of a blueprint that define the cloud resources and configurations for deploying VMs or applications. Substrates can be associated with different cloud accounts, such as AWS, Azure, GCP, or Nutanix, to enable multicloud deployments. By using substrates, an administrator can create a blueprint that can deploy VMs to multiple clouds, depending on the availability, cost, or performance requirements.

References:

Nutanix Multicloud Automation Administration (NMCAA) course, Module 3: Blueprints, Lesson 3.2: Substrates1

Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, Section 2.1: Create a blueprint to deploy infrastructure and applications using Nutanix Calm2

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

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

To share a Runbook across projects in Nutanix Calm, it should be published to the Calm Marketplace. The Calm Marketplace allows administrators to publish and share blueprints, runbooks, and other resources, making them available for use across different projects within the organization.

References:

Nutanix Calm documentation on Marketplace Publishing.

Nutanix Best Practices for Sharing Runbooks.

A category is a key-value pair that can be assigned to an entity in Prism Central to simplify daily operations and management. Categories can be used to filter, search, and group entities based on common attributes. Categories can also be used to define policies and permissions for different entities. A category can be assigned to a cluster, a VM, an image, a network, a blueprint, an application, or a project. A category cannot be assigned to a hypervisor, a protection domain, or a storage container, as these are not entities in Prism Central. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 12; Nutanix Prism Central Guide, section 4.1.

To create an alert for idle VMs, the administrator needs to specify the following parameters:

Scope: Select the category value Environment:Production to filter the VMs that are affected by the alert.

Metric: Select CPU Usage (%) as the metric to monitor the VMs’ CPU utilization.

Condition: Select Less Than as the operator and enter 5 as the threshold value to define the idle state.

Duration: Enter 5 as the duration value and select Minutes as the unit to set the time period for the idle state.

To create a Playbook with the alert as the trigger, the administrator needs to do the following steps:

Name: Enter a descriptive name for the Playbook, such as Idle VM Alert.

Trigger: Select Alert as the trigger type and choose the alert that was created for idle VMs.

Action: Select Email as the action type and enter the recipient email address, subject, and message for the notification.

The Playbook will run whenever the alert is triggered and send an email to the administrator informing them about the idle VMs.

References:

Nutanix Certified Professional Multicloud Automation (NCP-MCA) 6 Exam, page 9

Nutanix University - NCP-MCA 6 Exam Prep - Alerts and Playbooks

A Category in Nutanix is a grouping of entities (such as VMs, hosts, clusters, etc.) into a key-value pair. Categories are used to organize and manage resources more effectively by tagging them with meaningful identifiers.

References:

Nutanix documentation on Categories.

Nutanix Best Practices for Using Categories.

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

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.

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:

Adding a task within the service to ask for user and password at runtime is redundant and unnecessary, as the runtime-editable variables can already provide this functionality.

Creating a task script to login with ssh to GitLab and create a random user and password is not a good practice, as it exposes the GitLab server to security risks and does not use the REST API that GitLab provides for user management. References:

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”

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.

 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. 

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.

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

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

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 error message "A specified logon session does not exist. It may already have been terminated" is often caused by the lack of CredSSP (Credential Security Support Provider) being enabled on the Windows Operating System. CredSSP is necessary for certain remote operations, including executing PowerShell scripts remotely.

References:

Microsoft documentation on Enabling CredSSP.

Nutanix documentation on Troubleshooting PowerShell Scripts.

Categories in Self-Service (formerly Calm) are metadata labels that are assigned to cloud resources. These categories help organize and manage resources by tagging them with specific attributes, making it easier to apply policies and manage the infrastructure.

References:

Nutanix Calm documentation on Using Categories.

Nutanix Best Practices for Category Management.

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.

The image shows a failed status for an SSH_VM_Task, which is manually triggered. Since the task involves SSH, it’s likely that the IP Address SSH action has a timeout of 5 minutes, causing the playbook to fail if it cannot complete within this time frame. The IP Address SSH action is used to execute commands on a remote VM using SSH. It requires the IP address, username, password, and command to run as inputs. The timeout parameter specifies how long the action will wait for the command to finish before aborting. If the timeout is too short, the action may fail due to network latency, slow execution, or other factors. References:

Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam, page 16, section 1.3.2.2: “Playbooks”

[Nutanix University: NCP-MCA 6.5 Exam Prep - Playbooks], video 4: “Playbooks”

A Playbook is a feature of Nutanix Calm that allows you to automate tasks based on certain triggers or events. You can use a Playbook to create a workflow that monitors the storage capacity of the cluster and sends an email notification to the IT Director when the capacity reaches a certain threshold. You can also use the Playbook to generate a forecast report that shows the projected storage usage and availability based on historical data and trends.

References:

Nutanix Support & Insights, section “Playbooks”

Managing Storage Resiliency is now Simpler than Ever - Nutanix, section “Updates to the Storage Summary Widget”

Alert on resilient capacity of a cluster | Nutanix Community, section “What you can do is enable (check the warning checkbox) for this alert policy”

You can upgrade Nutanix Calm or Epsilon (the orchestration engine used by Nutanix Calm) by using the Life Cycle Manager (LCM) from the Prism Central. LCM allows you to upgrade Calm or Epsilon independently or simultaneously. You can also select the version that you want to upgrade to and perform the update from the Options list. For more information, see the Nutanix Calm Upgrades section in the Nutanix Calm Admin and Operations Guide1 and the Performing Inventory and Upgrading Calm with Life Cycle Manager article2. References:

Nutanix Calm Admin and Operations Guide1

Performing Inventory and Upgrading Calm with Life Cycle Manager2

When a task fails in a Multi VM Blueprint deployment within Nutanix Calm due to an issue such as a typographical error, and the error has been corrected, the administrator has options to handle the situation without needing to start the entire process from scratch.

According to Nutanix Calm documentation, the appropriate action after fixing the error is to choose the "Retry task" option. This allows the deployment process to continue from the point of failure, saving time and resources as opposed to deleting and relaunching the entire application or moving the blueprint to another project.

References:

Nutanix Calm Administration Guide

Nutanix Calm Troubleshooting and Best Practices