NCP-MCA Nutanix Certified Professional - Multicloud Automation (NCP-MCA 6.10) Exam Questions and Answers

Nutanix Self-Service defines several user roles, each with specific permissions.

Documentation describes theConsumerrole as:

Allowed todeploy applications from the Marketplace or assigned blueprints

Allowed to performday-2 operations(power actions, snapshots, etc.)

Restricted from modifying blueprints, environments, or project configurations

Ideal for end users who need access to deploy and manage their workloadswithout administrator capabilities

This matches exactly what the DevOps team requires.

Why the other roles are incorrect

Developer (A):Can modify blueprints and environments — too much privilege.

Project Admin (C):Full control over project resources — far more access than needed.

Operator (D):Used for automation and operational oversight, not end-user VM deployment.

Thus,Consumer (B)is the correct and intended role.

To configure a Playbook to run with the permissions of a specific user rather than the default system context, the creator uses theExecute on behalf offeature.

Context:By default, Playbooks in Intelligent Operations (X-Play) may run with system-level privileges. However, for audit compliance or specific access control requirements (e.g., when an action involves an API call that requires specific user credentials or a ticket creation that needs a specific "Requester"), the administrator can configure the execution context.

Configuration:In the Playbook settings menu, the"Execute on behalf of"option allows the administrator to select a specific Prism Central user. When the Playbook is triggered, all actions within it are executed and logged as if that specific user had performed them manually.

In Nutanix Self-Service (formerly Calm),Macrosare used to reference variables within scripts, task definitions, and configurations. The documented syntax for all macros requires the variable name to be enclosed within double "at" symbols and curly braces.

Syntax:@@{variable_name}@@

Usage:This format is used for both user-defined variables (e.g., @@{db_password}@@) and built-in system macros (e.g., @@{address}@@, @@{calm_time}@@, @@{calm_project_name}@@).

Evaluation:When the Self-Service engine executes a task, it parses the string, identifies the pattern @@{...}@@, and substitutes it with the actual value of the variable from the current context before sending the script to the target machine.

To make a specific task available for reuse across other blueprints and runbooks, an administrator can publish the task to the Task Library.

While working within the Blueprint or Runbook editor, an administrator can select a specific task they have configured. In the configuration pane for that task, there is an option to"Publish to Library". Selecting this saves the task (including its script and settings) to the central Task Library. Once published, the task appears in the Library list and can be imported into other blueprints or runbooks, ensuring consistency and reducing duplicated effort.

Self-Service Domain-Specific Language (DSL)is the specific capability within Nutanix Self-Service (formerly Calm) that enablesInfrastructure-as-Code (IaC).

Definition:The Self-Service DSL is a Python-based domain-specific language that allows administrators and developers to define Blueprints, Runbooks, and Projects as code.

Functionality:Instead of using the Graphical User Interface (GUI), users can write Python code to describe the application structure, services, and logic. This code can then be version-controlled (e.g., in Git), reviewed, and deployed via the CLI, fulfilling the principles of Infrastructure-as-Code.

Contrast:While "Application Development" and "Orchestration" are broad concepts, theDSLis the specific tool/feature that delivers the IaC mechanism.

In Nutanix Self-Service (Calm), Macros are used to reference variables and properties dynamically using the syntax @@{Entity.Attribute}@@.

Servicesare a primary supported entity for macros. You can reference properties of other services within the same application blueprint. For example, a web server service might need the IP address of a database service. This can be achieved using a macro like @@{Database_Service.address}@@. This allows for dynamic orchestration where values are populated at runtime based on the actual deployment details of the Service entity.

InIntelligent Operations (X-Play) Playbooks, the syntax for string interpolation (using parameters) differs from Self-Service (Calm).

Playbook Syntax:X-Play uses thedouble curly bracesyntax {{ ... }} to reference parameters.

Example:To reference the name of the entity that triggered the playbook, the correct parameter string is {{trigger[0].source_entity_info.name}} or {{trigger[0].alert_entity_info.name}} depending on the trigger type.

Contrast:@@{...}@@ (Option B) is the syntax used inSelf-Service (Calm)macros, not X-Play Playbooks.

In Nutanix Self-Service (formerly Calm), the Infrastructure tab within a Project is the designated location for configuring and assigning provider accounts.

When an administrator navigates toProjects>[Project Name]>Infrastructure, they can click"Add Infrastructure". This workflow presents the option to select:

Account:Cloud provider accounts (e.g., Nutanix AHV, AWS, Azure, VMware) that the project is allowed to use.

Credential Provider:External credential stores (if configured) or specific credential provider accounts that the project users can access for authenticating workloads.

The other tabs serve different purposes: "Users & Groups" handles RBAC, "Policies" handles Quotas and Approvals, and "Tunnels" handles VPC network connectivity.

To automate a notification based on a specific change in the environment (such as a VM powering off), the administrator should leverageIntelligent Operations (X-Play)by creating an event-driven Playbook.

Event Trigger:The "VM Power Off" or "Power State Change" is a system-generatedEvent. X-Play allows administrators to select this specific event as aTrigger. This ensures the automation runs in real-time immediately when the state change occurs, rather than waiting for a schedule (as in Option A).

Action (Slack):X-Play includes a nativeSlackaction (or "Send to Slack"). The administrator configures this action with the Slack Webhook URL and the desired message content.

Why not others?

Option Ais reactive and delayed (polling every 6 hours).

Option Bonly runs once during the initial deployment of the blueprint, not continuously during the VM's lifecycle.

Option Csuggests a Webhook trigger, which requires anexternalsystem to invoke the Playbook. Here, the event originatesinternallywithin Nutanix, so an Event Trigger is the correct choice.

To fully validate the integration between a Self-Service Project and a Playbook, the administrator must perform a test deploymentwithin the specific Project context.

Project Context:Playbooks often rely on triggers (like Categories) or parameters that are applied specifically by the Project's environment settings. Running the Playbook independently (Option A) only tests the script logic, not the trigger or the project-specific inputs.

End-to-End Validation:By deploying the blueprint associated with the Project (Option D), the administrator confirms:

The Project correctly provisions the resources (Quotas/Environment).

The Resources receive the correct Categories/Tags from the Project.

The Playbook Trigger successfully fires upon detecting these specific Project-derived events.

The Playbook executes successfully.

This is the only method that validates "both the Project and Playbook configurations" as a unified workflow.

When troubleshooting or optimizing blueprints where complex operations (like Provisioning combined with detailed Network Configuration) frequently fail, the recommended best practice is to split the steps into smaller tasks.

In Nutanix Self-Service (Calm), theAudittab provides a sequential log of every task executed during an application's lifecycle. If provisioning and network configuration are bundled into a "single step" (e.g., a large script or a single package install), a failure makes it difficult to determine if the issue was with the VM creation, the OS boot, or the specific network parameter application.

By splitting the logic into distinct tasks (e.g., Task 1: Provision VM, Task 2: Configure Network), the administrator can:

Isolate the failure:The Audit log will clearly show "Provision VM: Success" and "Configure Network: Failed".

Validate inputs:It ensures the VM is fully available before attempting configuration.

Improve Auditing:Granular logs allow for faster root cause analysis of the "misconfigured parameters."

Retrying (Option B) or adding delays (Option D) are reactive measures that do not address the root cause of configuration errors, and disabling logging (Option C) hinders troubleshooting.

According to theSelf-Service Administration and Operations Guide(specifically the section on System Limits and Maintenance), the retention policy for soft-deleted entities is explicitly defined:

Retention Period:"Data related to deleted apps and blueprints is cleaned up after3 months."

This mechanism is part of the internal database maintenance ("garbage collection") to manage resource usage on the Prism Central/Self-Service VM while allowing for audit trails or recovery within a reasonable window.

When configuring aNutanix(AHV) provider account within Self-Service (formerly Calm) to deploy infrastructure, the fundamental artifact required for VM provisioning is anAHV Image.

AHV Image:Nutanix AHV uses theImage Serviceto manage disk images (typically in QCOW2 or ISO format) that serve as the base for virtual machines. Before a Blueprint can be designed or deployed on a Nutanix account, a validDisk Imagemust be uploaded to the Prism Central Image Service. This image is then referenced in the Blueprint's VM configuration (Substrate) as the "Disk Image" source.

Contrast with other Providers:

VMware Template (Option B):This is the required artifact for theVMware vSphereprovider.

VHD (Option A):Typically associated with Hyper-V or Azure.

OVA (Option C):An export format, not a direct provisioning source for the Nutanix provider within Self-Service.

Therefore, ensuring anAHV Imageexists and is available on the cluster is the specific pre-configuration requirement for the Nutanix provider.

The scenario describes a "Zero Trust" style Security Policy (Flow Network Security) where all traffic is blocked unless explicitly allowed by a rule matching a Category.

The Rule:The policy specifically states that SSH (port 22) traffic is allowedonlyfor VMs tagged with the category AppType: Admin-VM.

The Issue:The deployed VM cannot be accessed via SSH. This indicates that the VM does not match the allow rule.

The Fix:The Blueprint used to deploy these Administrator VMs must be updated toassign the AppType: Admin-VM categoryto the VM service definition.

Once the VM is deployed with this tag, the Flow Security Policy will recognize it and permit the inbound SSH traffic. Assigning Web-Servers (Option B) would open port 443, not 22.

To troubleshoot why a post-deployment automation workflow (Playbook) is not executing, the administrator should investigate the specific execution records and the trigger configuration:

Check Playbook Execution History (C):The Playbook "Plays" or execution history (found in the Intelligent Operations or Self-Service Audit tab depending on the specific type of playbook used) provides the definitive record of whether the system attempted to run the automation. If the playbook appears in the history with a "Failed" status, the logs will indicate which specific step (e.g., HTTP task or API call) failed. If it does not appear at all, the issue lies in the trigger.

Verify Invocation (D):If the playbook is intended to run "post-deployment," it must be explicitly triggered.

ForX-Play Playbooks, this involves verifying theTriggerlogic (e.g., ensuring the "VM Created" event filter matches the specific Project Categories assigned to the new VMs).

ForSelf-Service (Calm) Runbooks, this involves verifying that the blueprint's "Post-Create" or "Profile" actions are correctly configured to call the Runbook.

Confirming these settings ensures the automation is properly "hooked" into the deployment lifecycle.

Reviewing VM creation logs in Prism Element (Option B) only confirms the VM was built (which is already known), and reassigning the project (Option A) is a destructive test that does not isolate the automation logic.

Comprehensive and Detailed Explanation

Nutanix Playbooks can start based on anAlert Trigger, which is defined as:

A specificPrism Central alertthat, when generated, automatically starts the Playbook.

Alert Triggers map directly to an alert definition that Calm will monitor.

Thus, the Alert Trigger doesnotgenerate alerts or notify admins by itself—itwaits for a selected alertand launches the Playbook when that alert fires.

Correct answer:D

To efficiently identify the source Blueprint for every VM created during a test, the administrator should utilize the built-inBlueprint Name Macrowithin a Multi-VM structure.

Macro Usage:The macro @@{calm_blueprint_name}@@ automatically resolves to the name of the blueprint being deployed (e.g., "Test_BP_Version_A").

Efficiency:By using aMulti-VM blueprint(which creates all four VMs in one deployment action) and configuring theVM Namefield in the service definition to include this macro (e.g., VM-@@{calm_blueprint_name}@@-@@{calm_array_index}@@), the administrator ensures that every resulting VM is automatically tagged with its source blueprint name in the hypervisor (Prism Element/Central) list.

Why not others:

Option Ainvolves "Single VM Blueprint" and "cloning," which is a manual or secondary process that is less efficient than a native Multi-VM definition.

Option Cuses @@{calm_application_name}@@, which identifies the specificinstance(e.g., "App-1"), not theblueprint design(e.g., "Web-Server-v2") that is being tested.

In the Nutanix Self-Service (Calm) Blueprint lifecycle, tasks are executed in a specific order relative to the provisioning of the infrastructure (Substrate).

Pre-Create Task:This is the specific phase designed to run scripts or set variablesbeforethe VM provision call is sent to the provider (AHV).

Workflow:

The developer creates a pre-create task (e.g., a Python script) to generate the custom hostname string based on logic (e.g., date, user input, or sequence).

The script outputs this string to a variable (e.g., @@{vm_hostname}@@).

The VM Service configuration (Substrate) references this variable in the "VM Name" or "Hostname" field.

Execution:When the blueprint launches, the pre-create task runs first, populates the variable, and then the VM creation occurs using that calculated name.

Tasks in post-create or package-install (Options B and C) runafterthe VM has already been provisioned and named, making them too late for this requirement.

TheLibraryin Nutanix Self-Service (formerly Calm) serves as a central repository for reusable automation assets that can be shared across multiple Blueprints and Projects. According to the Self-Service Administration Guide, the Library specifically contains:

Tasks (Scripts):The "Task Library" allows administrators to save Shell, PowerShell, Python (eScript), or HTTP tasks. These published tasks can then be imported into any blueprint, ensuring code reusability and standardization.

Variable Types (Variables):The Library also hostsVariable Types(often simply referred to as user-defined variables in the context of the library). Administrators can create and save complex variable definitions (such as lists or static values) in the Library to be reused in different blueprints without redefining them every time.

Endpoints(Option C) are configured in the global Settings or Project settings, not within the Library tab.Apps and Blueprints(Options A and D) have their own dedicated "Apps" and "Blueprints" tabs in the navigation bar.

Comprehensive and Detailed Explanation

Nutanix Calm supports OS customization throughGuest Customization, which:

AppliesSysprepfor Windows

Injects configuration files

Sets hostnames, time zones, networking, and more

Runs scripts post-deployment

Sysprep is specifically executed duringWindows Guest Customization.

Therefore,Option C: Guest Customizationis correct.

Nutanix Playbooks (part of Prism Central Automation) support multiple trigger types—Alert, Event, Webhook—and each trigger defines how automation workflows begin. The Nutanix Automation documentation highlights the following key rules:

1. Event Triggers (Correct Answer)

Playbooks using anEventtrigger supportmultiple playbook tasks, including script tasks, VM power operations, Prism actions, and more.

Nutanix documents specify that:

Event-based Playbooks activate when specificPC or cluster eventsoccur.

After an event trigger fires, administrators may definemultiple sequential actionsinside the Playbook.

This allows complex automation chains such as remediation actions, notification flows, or branching logic.

Therefore,Option D is correct, because Event-triggered Playbooks allow multiple actions to be added.

Why the other options are incorrect

❌Option A — Alert Trigger

Alert triggers only allowone alert definition per Playbook trigger.

Nutanix documentation states that an Alert trigger is mapped toa single alert policy, not multiple alerts.

Thus, Option A is incorrect.

❌Option B — Branch Step

ABranchisnot a trigger; it is aflow control elementusedafterthe Playbook has already started.

Branch steps define conditional paths but do not permit the addition of multiple "actions" as a trigger.

Therefore, Option B is incorrect.

❌Option C — Webhook Trigger

Webhook-triggered Playbooks start when external systems send an HTTP POST request.

While the Playbook may contain multiple tasks after triggering, the question specifically refers to addingmultiple scriptable tasks as part of the trigger, which is not possible.

Webhook triggers acceptonly one incoming webhook definition, not multiple script tasks embedded in the trigger.

Thus, Option C is incorrect.

Nutanix Self-Service (Calm) is designed to model complex applications using Multi-VM Blueprints.

To support a multi-tier stack (Web, App, DB) deployable in a single action:

Multiple Services:The administrator defines three distinct Services within the blueprint editor, one for each tier.

Dependencies:The administrator defines boot dependencies (e.g., Database must be up before App Server; App Server must be up before Web Server).

Single Action:Once published to the Project, the end-user sees a single catalog item. Clicking "Launch" triggers the orchestration engine to provision all VMs and configure them in the correct order automatically.

In Nutanix Self-Service (Calm), a Quota Policy limits the total infrastructure resources that can be consumed by a Project.5

When configuring a Project, the administrator sets limits for the following specific resources:

vCPUs:The total number of virtual CPUs allocated to VMs in the project.

Memory:The total amount of RAM (in GiB) allocated to VMs.

Disk:The total storage capacity (in GiB) allocated to VMs.

These quotas are enforced during the provisioning process. If a user attempts to launch a blueprint that would cause the project to exceed these defined limits (vCPU, Memory, or Disk), the deployment will fail. Quotas do not monitor IOPs, NIC counts, or the number of blueprints stored.

AProjectin Nutanix Self-Service (formerly Calm) acts as a logical container that defines the scope of operations for a group of users.

Primary Capability:The core purpose of a Project, once Self-Service is enabled, is to allow the users assigned to that project (Consumers, Developers, Operators) todeploy Blueprints(launch applications) andmanage the lifecyclesof the resulting workloads (VMs/Applications).

Scope:The Project restricts these users to specific Infrastructure (Clusters/VPCs), Environments, and Quotas defined by the administrator.

Exclusions:

Changing cluster-wide networking (A) and modifying global user roles (D) arePrism Admintasks, not capabilities granted to a Self-Service Project.

Managing global image repositories (B) is a Prism Central infrastructure task; Projectsconsumeimages but do not manage the global repository itself.

Nutanix Intelligent Operations (X-Play) allows administrators to create custom automation playbooks by defining triggers and associated actions. The system provides a library of pre-built actions to simplify integration.

To integrate notifications with standard collaboration platforms, the administrator should select theActionspecific to that platform. For example, theSlackandMicrosoft Teamsactions are natively available in the Action Gallery.

Slack Action:Requires entering a Slack Token and Channel Name.

Microsoft Teams Action:Requires entering a Webhook URL from the Teams instance.

Using these pre-built actions is the direct and recommended method for supported platforms, as opposed to configuring a generic Webhook manually (Option D) or modifying global settings (Option B).

Comprehensive and Detailed Explanation

Nutanix Self-Service requires aTunnel VMto establish communication between Prism Central and VPC-isolated workloads.

Documentation states that:

TheTunnel VM must be able to reach Prism Centralover a routable external network.

Anexternal subnetmust exist so the Tunnel VM can initiate outbound connectivity to PC.

Thus, the correct configuration is:

Create an external subnet to allow the Tunnel VM to reach Prism Central.

Therefore,Option Bis correct.

In a Nutanix Self-Service Blueprint, actions that affect theentire application lifecycleor its structural configuration are defined asProfile Actions.

Application Profile Actions:These are operations that run at the level of the Application Profile.

Custom Profile Actions:To enable capabilities likeScale Out(adding more replicas),Scale In(removing replicas), orUpgrade(updating the application software across the deployment), the developer createsCustom Profile Actions.

These actions are distinct from "Service Actions" (which apply to a single VM/Service, like "Restart Apache").

Once defined, these Custom Profile Actions appear as buttons on the "Manage" tab of the deployed application, allowing the application admin to trigger the scaling or upgrade workflows defined by the developer.