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

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.

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

Comprehensive and Detailed Explanation

Nutanix Calm documentation states:

TheBlueprint Editoris the graphical interface used to design, visualize, and modify a blueprint’s components, such as services, packages, substrates, dependencies, and tasks.

The editor provides avisual topologyof the multi-tier application.

Thus, the correct answer isC. Blueprint Editor.

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 satisfy specific ordering requirements around IP assignment (before VM existence) and Security Group assignment (after VM existence but before use), the administrator usesPre-createandPost-createtasks.

Pre-Create Task (IP Address):This task executesbeforethe VM provisioning call is made to the provider. The developer uses this phase (e.g., an HTTP task or Script) to request a specific IP from an external IPAM solution. The IP is stored in a variable and passed to the VM configuration.

VM Provisioning:The VM is created (using the IP from step 1) but is configured in the blueprint to stay in aPowered Offstate initially.

Post-Create Task (Security Group):This task executesimmediately afterthe VM resource is created (so the VM UUID/NIC exists) but before the application logic starts. The developer uses this phase to make an API call (e.g., to Flow or NSX) to place the VM into the required Security Group.

Power On:A subsequent task (or manual action) powers on the VM, ensuring it boots up with the correct IP and within the correct security boundary.

Option C is the only combination that covers both the "Before Creation" and "After Creation" phases required.

According to theSelf-Service Administration and Operations Guide(specifically the section on System Limits and Maintenance), the retention policy for soft-deleted entities is explicitly defined:

Retention Period:"Data related to deleted apps and blueprints is cleaned up after3 months."

This mechanism is part of the internal database maintenance ("garbage collection") to manage resource usage on the Prism Central/Self-Service VM while allowing for audit trails or recovery within a reasonable window.

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 Prism Central includesPredefined Playbooks(System Playbooks) that cover common use cases (e.g., "Email on Alert"). These system playbooks are protected templates.

Immutability:You cannot directly edit or modify a Predefined Playbook (making Option D incorrect).

Cloning Workflow:To customize a Predefined Playbook—such as adding an additional action step like "Slack Notification" or "VM Snapshot" at the end—the administrator mustClonethe playbook.

Process:Select the Predefined Playbook -> Click "Clone" -> Save as a new User Playbook. The administrator can then fully edit triggers and actions in this new copy.

While this effectively creates a "new" playbook (Option B), the specific mechanism provided in the interface and documentation to leverage the existing definition isCloning.

Nutanix Playbooks allowevent-driven automation.

Documentation states that Playbooks can:

Trigger onVM Powered Offevents

Filter targets usingcategories(e.g., OSType: Linux, Environment: Dev)

Perform actions such asVM Reduce CPU,VM Resize, etc.

To automatically and immediately update CPU count when the VM powers off, the proper method is:

✔Use aPlaybook

✔Trigger:VM Powered Off

✔Target VMs using categories

✔Action:VM Reduce CPU

Self-Service Runbooks (Option D) are manually executed; they do not automatically trigger on events.

Therefore,Option Cis correct.

Nutanix Self-Service (formerly Calm) uses Services, app profiles, packages, substrates, and actions as the building blocks for a blueprint to define applications.

AServiceis the core logical entity within a blueprint. An application is made up of multiple components (or services) working together, such as a Database Service and a Web Server Service. Each service defines the specific infrastructure (VM), software packages, and operations required for that component of the application.