Nutanix NCP-MCA Practice Test - Questions Answers, Page 12

The best option to automate the installation of the local agent on all Linux VMs is to create an Endpoint that includes all Linux VMs and include the Endpoint in a Runbook that executes a shell script for agent installation. This way, the administrator can leverage the Calm Runbook feature, which allows orchestrating tasks across multiple VMs without the need of a blueprint or an application. The administrator can also filter the VMs by name, tag, or other criteria to select the target VMs for the Endpoint. The shell script can be added as a task in the Runbook and run on the selected Endpoint.

Option A is not correct because a Brownfield deployment is used to create an application from existing VMs and an existing blueprint. It is not suitable for automating tasks across multiple VMs without a blueprint. Moreover, a Brownfield deployment cannot attach to post-Calm created VMs, as they are already managed by Calm.

Option C is not correct because creating a new golden image and deploying all VMs again is a very time-consuming and disruptive process. It also requires the administrator to migrate the data and configuration of the existing VMs to the new ones. This option does not leverage the Calm automation capabilities and is not recommended.Reference:Nutanix Calm Runbooks & API Automation,Nutanix Support & Insights,Calm 3.0 is Here!,Nutanix Cloud Manager

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

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

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.Reference:Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 12; Nutanix Prism Central Guide, section 4.1.

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

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 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.Reference:Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 12;Nutanix NCP-MCA Questions, question 111.

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

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

Test Script is a feature of Nutanix Cloud Manager (NCM) Self-Service that allows users to test or validate scripts before deployment. Test Script enables users to run scripts on a VM without creating a blueprint or a runbook. Users can select a VM, choose a script type, enter the script content, and execute the script. The output of the script is displayed in the Test Script window. Test Script can be used to troubleshoot errors, verify functionality, or preview the results of a script before using it in a blueprint or a runbook.Reference:Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 14, section 3.1.Nutanix Multicloud Automation Administration (NMCAA) course, module 3, lesson 4.Validate Your Nutanix Cloud Manager Self-Service Skills + Access Special Offer.

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.

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