Pass the Nutanix Nutanix Certified Professional (NCP) NCP-MCA Questions and answers with CertsForce

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.

Comprehensive and Detailed Explanation

Self-Service platform sync allows Prism Central to periodically collect updates from external providers.

Nutanix documentation states that the providers supportingplatform sync with a 20-minute update windoware:

Nutanix (AHV)

VMware (vSphere)

AWS

These environments support the metadata collection necessary for tracking:

IP changes

Disk resizing

VM availability

Thus, the valid set isNutanix, VMware, and AWS, makingOption Ccorrect.

When a Blueprint is designed to trigger external automation (like a Playbook via Webhook or API) or perform post-deployment actions (like applying categories via script), these actions must be explicitly defined asTaskswithin the Blueprint's lifecycle.

The Symptom:The VM provisioning (Substrate) succeeded, but the subsequent logic (Categories/Notifications) failed to happen.

The Cause:In Self-Service, simply creating a Blueprint does not automatically link it to an Intelligent Operations Playbook. The developer must add a specific task (e.g., an HTTP Request task targeting the Playbook trigger, or a specific "Execute Playbook" action) to theService Profile(specifically the Post-Create or Create phase).

If this task is missing, disabled, or misconfigured (e.g., wrong URL or payload), the VM will deploy, but the call to the Playbook will never occur, resulting in missing categories and notifications.

Option A is incorrect because deployment would not start at all without a Project. Option D is incorrect because Playbooks are not published to the Marketplace (Blueprints are).

In Nutanix Prism Central Disaster Recovery, when a Prism Central instance fails over to a recovered site, several automation components—including Playbooks—must be revalidated. Nutanix documentation clearly states:

Playbooks store encrypted credentials locally in the Prism Central database.

When Prism Central is recovered on a DR site, the credential encryption keys donottransfer.

As a result,any credentials previously stored in Playbooks become invalidand must be manually re-entered.

This requirement ensures that the scripts, tasks, remediation sequences, and integrations invoked by the Playbook can authenticate properly after recovery.

Therefore:

Playbookscannot automatically use previously stored credentialsafter a DR failover.

Administrators mustre-enter all credentialsin enabled Playbooks so the automation continues functioning.

Hence, OptionCis correct.

Options A and D are incorrect because Playbooks donotautomatically retain functional credentials after DR recovery.

Option B is incorrect because the presence or absence of a credential provider does not change the need to re-enter credentials.

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 (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 scale out a Self-Service (formerly Calm) deployment from a single Self-Service VM (SSVM) to a multi-node cluster, the administrator must follow a migration-style procedure rather than an in-place expansion. According to the Self-Service Administration and Operations Guide section onSetting up Scale-Out Self-Service VM:

Backup:The process involves destructive cluster commands, so the administrator must first take a backup of the existing Self-Service data.

Deploy New VMs:The administrator must deploythree new Self-Service VMsusing the provided OVA/template. This ensures a clean, uniform environment for the new cluster. (Adding nodes to an existing, potentially drifted single node is not the standard procedure).

Restore and Cluster:The administrator must then run the specific cluster creation commands (such as cluster create with the IPs of the three new nodes) andrestorethe Self-Service data and configuration from the backup to the new cluster to retain all projects, blueprints, and users.

While the exact order of "Restore" and "Cluster Create" involves technical nuance (creating the service capabilities then populating the data), the key differentiator is that the administrator must deploythree new SSVMs(Migrate) rather than just adding two to the existing one, and must explicit perform arestoreoperation to migrate the data.

According to the Self-Service Administration Guide regardingError Handling in Runbook and Blueprint Tasks, there is a specific documented limitation regarding VM Power actions.

General Behavior:The error handling mechanism is designed to allow workflows to continue or alert when tasks (including VM Power On/Off) fail for reasons such as the Prism Central being unreachable or the VM being deleted.

The Exception (Option D):The documentation explicitly states:"Error handling, however, does not take into account the power on, power off, or restart task failures because of authentication errors."

If the "VM Power On" task fails specifically due to an authentication issue (e.g., token expiry or connectivity preventing authentication with the host), the standard error handling flow may not trigger as expected, matching the scenario described.

Option A is incorrect because Self-Servicecanhandle infrastructure task failures (like Power On), with specific exceptions like the one noted in D.

Playbooks in Intelligent Operations (X-Play) areEvent-Driven. They execute strictly when a specific event (trigger) occurswhilethe playbook is active.

The Scenario:The administrator sees the category Expired is present on the VM, and the Playbook is currently enabled.

The Cause (Option B):If the category was applied to the VMwhile the Playbook was disabled(or before it was created), the system generated the "Category Assigned" event, but the Playbook was not listening for it at that time.

Consequence:When the administrator later enables the Playbook, it does not retroactively scan for existing VMs with that category; it only waits fornewassignment events. Since the event was missed, no execution record exists.

To fix this, the administrator would need to re-apply the category (remove and add) while the Playbook is enabled to generate a new event.

In Nutanix Self-Service (Calm), when defining a variable for a Runbook (or Blueprint), there is a specific configuration attribute called "Runtime".

Runtime Editable:If this checkbox is selected during the variable creation, the user executing the Runbook will be prompted to provide or modify the value at the time of execution.

Not Runtime Editable:If this checkbox is left cleared (unchecked), the variable uses the default value defined by the administrator, and the user executing the Runbookcannot changethis value.

Therefore, if the administrator cannot change the value during execution, it is because the variable was not marked as runtime editable in the Runbook definition.