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

To successfully create, validate, and publish blueprints to the Self-Service Marketplace (formerly Calm Marketplace), aProjectmust be configured with the following two essential components:

Infrastructure (A):

The Infrastructure configuration (often found under the "Infrastructure" or "Accounts" tab in the Project settings) is the foundational requirement. It allows the administrator to select which Cloud Provider accounts (such as Nutanix AHV, VMware vSphere, AWS, Azure, or GCP) are available for use within that specific project. Without configuring Infrastructure, the project has no access to resource providers, and therefore no blueprints can be created or validated for publication.

Environments (B):

The Environment configuration is critical for the "Blueprint to Marketplace" workflow. An Environment defines the specific compute, network, and storage profiles for the infrastructure selected in the project (e.g., mapping a specific AHV Cluster and Network to the project).

During Creation:A blueprint relies on the Project Environment to define its platform-specific settings (like Images and Networks) while being designed and tested.

During Publication & Launch:When a blueprint is published to the Marketplace, it is often published "without platform-dependent configuration" to make it portable. This portability relies entirely on the destination Project having a configuredEnvironment. When a user launches a Marketplace item, the Self-Service engine "patches" the abstract blueprint requirements with the concrete details (Network, Cluster, Credentials) defined in the Project'sEnvironment.

Policies (C)(such as Quotas and Approvals) andTunnels (D)(used for network connectivity in hybrid/VPC scenarios) are optional configurations and are not strictly required to publish a blueprint to the marketplace.

The image typically displays the Project configuration tabs: "Users, Groups, & Roles," "Infrastructure," "Environments," "Policies," and "Quotas," visually confirming the hierarchy where Infrastructure and Environments are the primary configuration steps for resource definition.

TheLibrary(specifically theTask Library) is the designated repository in Nutanix Self-Service for creating and managing reusable automation building blocks.

Task Library:This feature allows administrators to define discrete tasks (such as Shell scripts, PowerShell scripts, HTTP requests, or Python scripts) once and store them centrally.

Reusability:These tasks serve as fundamental "building blocks" because they can be imported into multiple Blueprints and Runbooks across different Projects.

Differentiation:

Tasks (Option C):While "Tasks" are the actual units of work, the question askswherethey are created for the purpose of establishing them as foundational, reusable blocks. They are createdin the Library.

Projects (Option B):Projects are logical containers for users, quotas, and environments, not the repository for reusable script definitions.

Thus, theLibraryis the correct location for creating shared automation assets.

AProjectin Nutanix Self-Service (formerly Calm) acts as a logical container that defines the scope of operations for a group of users.

Primary Capability:The core purpose of a Project, once Self-Service is enabled, is to allow the users assigned to that project (Consumers, Developers, Operators) todeploy Blueprints(launch applications) andmanage the lifecyclesof the resulting workloads (VMs/Applications).

Scope:The Project restricts these users to specific Infrastructure (Clusters/VPCs), Environments, and Quotas defined by the administrator.

Exclusions:

Changing cluster-wide networking (A) and modifying global user roles (D) arePrism Admintasks, not capabilities granted to a Self-Service Project.

Managing global image repositories (B) is a Prism Central infrastructure task; Projectsconsumeimages but do not manage the global repository itself.

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.

Among the options provided, calm_unique is the standard built-in macro provided by the Self-Service engine.

Purpose:The @@{calm_unique}@@ macro generates a unique, short alphanumeric string at runtime.

Use Case:It is widely used in Blueprints to ensure uniqueness for VM names, hostname prefixes, or other resources that cannot have duplicate identifiers within the infrastructure (e.g., naming a VM Web-@@{calm_unique}@@ to prevent naming collisions).

Other Options:calm_date, calm_generate_uuid, and calm_math are not standard built-in macro names in the Self-Service macro library (though calm_time and calm_now exist for time-based operations).

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.

The requirement to restrict VMs to specific physical hosts for licensing purposes is addressed usingVM-Host Affinity Policiesin Nutanix AHV, which relies onCategories. The complete configuration workflow is:

Categorization (Step 1):The administrator must create specific categories to tag the entities. One category (e.g., License:Oracle) is assigned to the specificHosts(the licensed ones). Another category (e.g., App:Database) is created for theVMs.

Affinity Policy (Step 2):An Affinity Policy is created in Prism Central that strictly enforces that any VM with the App:Database category must run on hosts with the License:Oracle category.

Blueprint Assignment (Step 3):In the Self-Service Blueprint, the administrator configures the VM service to automatically apply the App:Database category upon creation.

When the blueprint is deployed, the VM is created with the category, and the AHV scheduler immediately respects the Affinity Policy, ensuring the VM only starts on the licensed hosts.

Options A and C are incomplete (Categories alone do not enforce placement), and Option B (Playbook migration) is a reactive "fix" rather than a proactive placement constraint, which risks non-compliance at startup.

The feature within Nutanix Self-Service (Calm) designed specifically for publishing blueprints to end-users is theMarketplace.

Marketplace:This component acts as an app store for the organization. Administrators and developers create Blueprints and thenpublishthem to the Marketplace.

Process:The "Marketplace and Application Management" capability encompasses the workflow of submitting a blueprint for approval, versioning it, and making it visible to users based on their Project entitlements.

Consumption:Once published, users do not access the raw blueprint design canvas; instead, they access the Marketplace Item to launch (consume) the application.

While "Unified Multi-Cloud Orchestration" describes the platform's broad goal, and "DSL" is a method for creating code-based blueprints, "Marketplace" is the specific functional area for publishing and consumption.