NCP-MCA Exam Dumps - Nutanix Certified Professional - Multicloud Automation (NCP-MCA 6.10) Exam

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

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.

In Nutanix Cloud Manager (NCM) Intelligent Operations (formerly Prism Pro/X-Play), the primary method for troubleshooting and validating Playbook behavior is through the Plays view in Prism Central.

When a Playbook is reported as not executing as expected, the administrator must examine thePlaystab (Execution History). This view provides a detailed log of all playbook activity, including:

Status:Whether the playbook succeeded, failed, or is in progress.

Trigger Details:Information regarding what specific event or alert triggered the playbook. If the playbook is not running at all, the administrator needs to verify if the "Idle VM" trigger conditions (e.g., CPU usage threshold, duration) are actually being met by the VMs in question.

Step-by-Step Execution:If the playbook triggered but failed during execution, the history details exactly which step failed and provides error messages (e.g., permission issues or API failures).

Options such as rebooting Prism Central or increasing quotas do not address the need to diagnose why specific automation logic failed to fire or complete. Modifying the execution context is a potential fix onlyafterthe execution history reveals a permission error, but checking the history is the mandatory first step to validate the configuration.

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 automate the provisioning of a VM and the subsequent application installation within a Nutanix Self-Service (Calm) Blueprint, the administrator must configure a Service.

The definition of a Service in a blueprint involves three distinct components to achieve this requirement:

VM Resource:Configuring the underlying infrastructure specifications (vCPUs, Memory, Disks).

Guest Customization:Configuring Cloud-init (Linux) or Sysprep (Windows) to handle the initial OS bootstrap (hostname, user creation).

Tasks (Package Install):Adding a script task (e.g., Shell or PowerShell) under the "Service Installation" action or a dedicated Package install step. This task executesafterthe VM is provisioned and running to install the web server application.

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.

In Nutanix Self-Service (Calm), to share a Runbook across multiple projects, it must be published to the Marketplace.

When an administrator selects an existing Runbook and chooses the "Publish" option:

Secret Handling:The system strictly enforces thatsecrets (passwords/keys) are not published. The administrator is required to verify that no secret values are hardcoded. Any sensitive variables are stripped or must be set to runtime input during the publication process.

Project Selection:During the publication or approval workflow via theMarketplace Manager, the administrator configures theProject Sharingsettings. This determines which projects have access to view and execute the Runbook from the Marketplace.

It is not necessary to clone the Runbook first; the publication process itself creates the Marketplace entry derived from the source Runbook.