Nutanix Certified Professional NCP-MCA Updated Exam

When creating a variable in a Nutanix Self-Service Blueprint or Runbook, the administrator must select aData Type. The standard supported data types areString,Integer,Date,Time, andDateTime.

String (Single-line):This is the fundamental text data type (typically just labeled "String" in the UI). It is used for standard alphanumeric inputs.

Input Options:While a String variable can be configured with an attribute to accept "Multi-line" input (useful for SSH keys or scripts), the base data type itself isString(which defaults to single-line).

Invalid Options:"Multi-line integer" is not a valid type. "Year Month Day" is a format description, not the name of theDatedata type. Therefore,Single-line string(representing the standard String type) is the correct available option among the choices.

In Nutanix Self-Service (Calm), the Marketplace Manager is the specific administrative view used to govern the publication of blueprints.

When a developer submits a blueprint for publication, it enters a "Pending Approval" state. An administrator must access theMarketplace Manager, navigate to theApproval Pendingtab, and explicitly approve the blueprint. Only after this approval does the blueprint become visible to end-users in the standard Marketplace.

"Approval Policies" (Option C) refer to runtime restrictions (e.g., requiring approval toprovisiona VM), not the pre-publication governance of the blueprint design itself.

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.

Nutanix Prism Central includesPredefined Playbooks(System Playbooks) that cover common use cases (e.g., "Email on Alert"). These system playbooks are protected templates.

Immutability:You cannot directly edit or modify a Predefined Playbook (making Option D incorrect).

Cloning Workflow:To customize a Predefined Playbook—such as adding an additional action step like "Slack Notification" or "VM Snapshot" at the end—the administrator mustClonethe playbook.

Process:Select the Predefined Playbook -> Click "Clone" -> Save as a new User Playbook. The administrator can then fully edit triggers and actions in this new copy.

While this effectively creates a "new" playbook (Option B), the specific mechanism provided in the interface and documentation to leverage the existing definition isCloning.