NCP-MCA Nutanix Certified Professional - Multicloud Automation (NCP-MCA v6.5) Exam Free Practice Exam Questions (2025 Updated)

When scripts are not specified under the Stop service-level actions, the system does not generate orchestration edges automatically. To prevent this issue, the administrator should manually update all system-defined actions. This involves defining the necessary scripts or actions to ensure proper orchestration and dependencies are in place.

References:

Nutanix documentation on Service-Level Actions.

Nutanix Best Practices for Orchestration Management.

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

 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

 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:

The AMIS tab shows the list of Amazon Machine Images (AMIs) that are available for the blueprint. The administrator can use this tab to select an AMI for the blueprint or create a custom AMI.

The service tab shows the list of services that are part of the blueprint. The administrator can use this tab to add, edit, or delete services, as well as configure the dependencies, tasks, and variables for each service.

The Metrics tab shows the performance metrics of the blueprint, such as CPU, memory, disk, and network usage. The administrator can use this tab to monitor the health and performance of the blueprint and its services. References:

Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam, page 18

Nutanix Calm User Guide, section “Blueprint History”

A service dependency is a feature of Nutanix Calm that allows you to define the order of execution and the conditions for starting and stopping services in a blueprint. By creating a service dependency between the application and the database, you can ensure that the application will not start until the database is fully installed and ready. This avoids the need for manual intervention or inefficient workarounds like loops or sleep statements. References: Nutanix Multicloud Automation Administration (NMCAA), page 41; Nutanix Certified Professional - Multicloud Automation (NCP-MCA), section 2.

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

 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

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 administrator should use a trigger based on an event when creating a playbook to automate the scaling of the VDI solution. An event trigger is a type of trigger that executes a playbook when a specific event occurs in the Nutanix environment or in a third-party system. An event trigger can be configured to listen to events from various sources, such as Prism alerts, Calm actions, or external webhooks. In this scenario, the administrator can use an event trigger to listen to the webhook from the third-party monitoring tool and execute a playbook that creates additional resources and adds them to the VDI solution.

A trigger based on a REST API is not the best option, because it requires the administrator to manually invoke the playbook using an API call. This is not as efficient or reliable as using an event trigger that automatically executes the playbook when the capacity threshold is reached.

A trigger based on an email is also not the best option, because it requires the administrator to configure an email server and a mailbox to receive the notification from the third-party tool. This adds complexity and overhead to the automation process and may not be as secure or timely as using an event trigger.

A trigger based on an alert is a valid option, but it depends on the availability and compatibility of the Prism alert system with the third-party tool. If the third-party tool can send alerts to Prism, then the administrator can use an alert trigger to execute the playbook. However, if the third-party tool does not integrate with Prism, then the administrator cannot use an alert trigger and has to use an event trigger instead.

References:

Nutanix Calm User Guide: Chapter 8: X-Play

Nutanix Calm DSL User Guide: Chapter 5: Playbooks

Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide: Section 1: Describe and Differentiate Automation Concepts and Principles

To run a blueprint deployment and tasks in a different Prism Central instance than the one running Self-Service (formerly Calm), the administrator should add the remote Prism Central instance as an account. This configuration allows Self-Service to interact with multiple Prism Central instances, enabling the management and deployment of blueprints across different environments.

References:

Nutanix documentation on Managing Accounts in Calm.

Nutanix Best Practices for Multi-Cluster Management.

To update the running configuration for a multi-VM application in AWS using the Manage tab for the application in Calm, the administrator needs to provide the provider information for the AWS account. This includes the access key, secret key, region, and VPC ID. If the provider information is missing, the administrator will not be able to perform any actions on the application from Calm. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 16, section 4.1.1.