NCP-MCA Exam Study Guide: The Ultimate 2026 Practice Test

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 the Marketplace Manager , navigate to the Approval Pending tab, 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 to provision a VM), not the pre-publication governance of the blueprint design itself.

To automate actions based on a signal from a third-party monitoring tool, the administrator should use the Webhook Trigger in Nutanix Intelligent Operations (X-Play).

Webhook Trigger: The administrator creates a playbook that starts with a Webhook Trigger. This generates a unique URL.

Integration: The third-party tool is configured to send an HTTP POST request (the notification) to this unique URL when the "low capacity" threshold is reached.

Automation: Receiving this signal automatically triggers the playbook to execute the expansion tasks (e.g., calling APIs to provision more VDI nodes or expand storage), removing the manual step.

While "Alert" (Option D) is used for native Nutanix alerts, the "Webhook" is the designated mechanism for receiving external events.

To enforce different configurations for different types of workloads within the same Project, Nutanix Self-Service uses Environments .

Environments: These are logical configurations within a Project that map to specific infrastructure settings. An administrator can define multiple environments (e.g., "Development" and "Production") within the "Engineering" project.

Category Assignment: Within each Environment configuration, the administrator can define specific VM Categories that will be automatically applied to any VM provisioned into that environment.

Mapping:

Production Environment: Assign the category Protection: async_1hr_repl (Matches requirement: Asynchronous remote replication every 1 hour).

Development Environment: Assign the category Protection: snap_24_hr (Matches requirement: Daily snapshots).

Execution: When a user launches a blueprint, they select the target Environment (Dev or Prod). The system automatically tags the VMs with the categories defined in that environment, which in turn engages the Protection Policies associated with those tags.

Option B uses the wrong category values (sync_remote_repl instead of async). Options C and D suggest using Playbooks, but the native and most efficient method for applying deployment-time governance in Self-Service is via the Project Environment settings.