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

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.

The visibility of clusters within a Self-Service Project is strictly controlled by theInfrastructure(or Accounts) configuration within the Project settings.

Infrastructure Whitelisting:When configuring a Project, the administrator must select which Accounts and Clusters are available for use. This is often referred to as defining theProject Scopeor whitelisting infrastructure.

The Cause:If users can see and create Environments targeting "Production Clusters," it is because the administrator explicitly selected (whitelisted) those Production Clusters in the Project's Infrastructure tab.

Environments vs. Infrastructure:Environments are definitions createdusingthe allowed infrastructure. Option D is less accurate because you whitelist theInfrastructure(resources), and then Environments are created on top of them. The root cause of the resource availability is the infrastructure whitelist in the Project Scope.

Nutanix Disaster Recovery usesProtection Policiesto automate replication. These policies are applied to VMs dynamically based onCategories. To protecteveryVM from both blueprints described, the administrator must select a category that iscommon to bothsets of VMs.

Blueprint 1 Categories:OSType: Windows, AppType:IIS

Blueprint 2 Categories:OSType: Windows, Environment:Dev

Commonality:The category OSType: Windows is assigned in both blueprints.

Configuration:By creating a Protection Policy that targets the category OSType: Windows, any VM deployed fromeitherblueprint will automatically inherit this tag. Consequently, the Disaster Recovery engine will immediately detect the new VM and begin replicating it according to the policy (Asynchronous, 1 hour) without manual intervention.

Options B and D would only protect a subset of the VMs (only IIS servers or only Dev workstations, respectively).

TheeScript(embedded script) module in Nutanix Self-Service (Calm) utilizesPythonas its scripting engine.

Version Standard:As of recent versions (specifically post-3.8.0), support for Python 2 has been deprecated and revoked. The system exclusively supportsPython 3for all new eScript tasks in Blueprints and Runbooks.

Context:While eScripts run in a containerized environment that processes the script logic, Python 3 is the mandatory syntax and runtime environment for these tasks.

PowerShell (A):Supported as a separate task type ("PowerShell"), not as the language for the "eScript" task type.

The image typically shows the Task Editor window where "Type" is selected as "eScript" and the script editor pane clearly displays "Python 3" as the script type syntax highlighter.

To configure and enforce resource limits within a Nutanix Self-Service (formerly Calm) project, the specific governance component known as thePolicy Enginemust be active.2

According to the Self-Service Administration and Operations Guide regarding thePolicy Engine and Quotas Overview:

Enabling the Policy Engine:You enable and use the policy engine to enforce resource quota policies for infrastructure resources (compute, memory, and storage) on Nutanix and VMware accounts.3

Prerequisite status:Until the policy engine is enabled in the Admin Center Settings, Prism Central cannot perform any quota checks or validation on resource consumption.4

Availability:The options to define resource quota limits (such as vCPU, Memory, and Disk fields in the Project configuration)appear only when you enable the policy enginein your Prism Central instance.5If the policy engine is not enabled, the Quota section in the Projects pages remains unavailable.6

Nutanix Data Protection (Leap) and Flow Security policies rely on Categories to dynamically assign policies to entities.6

In this scenario, the administrator likely set up the Protection Policy to target the Protection: Silver category (standard practice for tiered Service Level Agreements, e.g., Gold, Silver, Bronze). While Environment: Prod is used for the Security Policy (isolation), the Protection Policy specifically requires the protection category to function as intended in a tiered architecture.

If the blueprint (Marketplace item) only assigned Environment: Prod, the VM is missing the critical tag (Protection: Silver) required to associate it with the 1-hour snapshot schedule. To fix this, the blueprint must be updated to assignbothcategories (Environment: Prod AND Protection: Silver) to the VM during provisioning.