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

Comprehensive and Detailed Explanation

When configuring aSelf-Service Account for AWS, Prism Central must be able to:

Resolve AWS service endpoint URLs

Validate API calls via name-based resolution

Nutanix documentation specifies thatDNS is requiredfor all cloud-provider integrations, including AWS, Azure, and GCP.

Therefore,DNSis the required network element.

Correct answer:B

In Nutanix Self-Service (Calm),Endpointsare external execution targets used by Playbooks and Runbooks to run scripts or automation tasks. Nutanix documentation specifies the followingvalid Endpoint types:

Windows Endpoint

Linux Endpoint

Database Endpoints(e.g., PostgreSQL, MySQL)

HTTP/Webhook Endpoints

Calm identifiesWindowsandLinuxmachines as valid, manageable Endpoints, meaning administrators can run scripts, commands, and automation tasks on them.

Why the correct answer is B (Windows)

Windows is explicitly listed as a supported Endpoint type.It supports script execution (PowerShell), credential storage, and remote orchestration through Calm.

Why the other options are incorrect

❌A. API Gateway

An API Gateway isnot an Endpoint typein Self-Service; it is not used for script execution or orchestration.

❌C. CentOS

Although CentOS is a Linux distribution, Calm doesnotregister distribution-specific Endpoints like "CentOS."

Instead, it uses thegeneric Linux Endpoint type, not OS-specific entries.

Therefore, "CentOS" isnota selectable Endpoint type.

❌D. Kubernetes

A Kubernetes cluster can be integrated with Nutanix, but it isnot classified as a Playbook/Runbook Endpointin Self-Service.

Kubernetes resources are handled through Calm Blueprints—not through Endpoint registration for automation tasks.

To use (leverage) a Dynamic Credential (provided by an external IPAM or Secrets solution like CyberArk or Vault) within a project, the administrator must configure theProject Environment.

Workflow:

Navigate to theProjectsettings and select theEnvironmenttab.

In theCredentialssection of the Environment configuration, clickAdd Credential.

Select theCredential Provider(Dynamic) rather than a Static credential.

Result:This action effectively "adds" the dynamic credential configuration to that specific environment, making it available for blueprints launched within that context.

Option A ("Allow credential provider") usually refers to theInfrastructuretab where accounts are whitelisted, but the specific configuration of the credential itself happens via the "Add" action in the Environment.

In Nutanix Self-Service,Projectsare the foundational organizational construct. Documentation states that Projects allow administrators to:

Groupusers and user groups

Assignroles(Consumer, Developer, Project Admin, etc.)

Defineresources(clusters, networks, images) allocated to that project

Attachblueprints, application profiles, and environments

Thus,Projects manage user grouping and role-based access, which matchesOption A.

Options B, C, and D do not represent Project functionality within Self-Service.

To provide users with access to Nutanix Self-Service (formerly Calm), an administrator must configure Role-Based Access Control (RBAC) within the context of a Project.

Access to Self-Service is not global; it is defined at the Project level.1An administrator must:

Add the user (or their Active Directory group) to a Project.

Assign a Roleto that user within the project.

Project Admin:Full control over the project.2

Developer:Can create blueprints and applications.

Consumer:Can only launch blueprints available in the Marketplace.3

Operator:Can perform day-2 operations on existing applications.4

Without an assigned role in a project, a user cannot access the Self-Service portal features or view any blueprints.

In Nutanix Self-Service Runbooks, tasks that execute scripts (such as Shell for Linux or PowerShell for Windows) require a target destination. This target is defined as an Endpoint.

AnEndpointconfigures the connection details (IP address, port, connection protocol, and credentials) required to communicate with the remote machine where the script will run. Without selecting a valid Endpoint, the Runbook engine does not know where to send the script for execution.

Nutanix Calm and Self-Service automation workflows require validation within the same execution context used by end users. Nutanix documentation specifies the following principles:

1. Playbook validation requires execution in the same user and project context

Playbooks that target resources using aCalmProjectcategory must be tested in the exact context in which they will operate.

The"Execute on behalf of"option allows the administrator to run the Playbookas if a project user initiated it, ensuring validation of:

Project-based scoping

User permissions

Category-based triggers

Playbook logic and automation flow

This matches the documented requirement that Playbooks must be validated under theintended user execution model, makingOption B correct.

2. Deployment must occur inside the Project to activate category-driven Playbooks

Blueprint deployments only trigger Playbooks when:

The deployment occursinside the Project, and

The VM receives metadata (such as CalmProject category) associated with that Project.

Nutanix Calm documentation highlights that Playbooks relying onProject categoriesonly activate when VMs are provisionedfrom that specific Project.

Deploying from the Marketplace does not guarantee that the correct project context or categories will be applied.

Thus, verifying Playbook execution requires deploying the blueprint assigned to the Project, makingOption D correct.

Why the other options are incorrect

❌Option A – “Execute”

This executes Playbooks only in the admin context, not the Project context. It doesnotvalidate permissions, user behavior, or category-based triggers required for Self-Service operation.

❌Option C – Marketplace deployment

Marketplace deployments do not necessarily apply Project-specific categories or metadata, so they cannot reliably test integration with Playbooks bound to a Project.

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

In Nutanix Self-Service (Calm), Macros are used to reference variables and properties dynamically using the syntax @@{Entity.Attribute}@@.

Servicesare a primary supported entity for macros. You can reference properties of other services within the same application blueprint. For example, a web server service might need the IP address of a database service. This can be achieved using a macro like @@{Database_Service.address}@@. This allows for dynamic orchestration where values are populated at runtime based on the actual deployment details of the Service entity.