Nutanix Certified Professional Changed NCP-MCA Questions

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.

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.

When configuring aNutanix(AHV) provider account within Self-Service (formerly Calm) to deploy infrastructure, the fundamental artifact required for VM provisioning is anAHV Image.

AHV Image:Nutanix AHV uses theImage Serviceto manage disk images (typically in QCOW2 or ISO format) that serve as the base for virtual machines. Before a Blueprint can be designed or deployed on a Nutanix account, a validDisk Imagemust be uploaded to the Prism Central Image Service. This image is then referenced in the Blueprint's VM configuration (Substrate) as the "Disk Image" source.

Contrast with other Providers:

VMware Template (Option B):This is the required artifact for theVMware vSphereprovider.

VHD (Option A):Typically associated with Hyper-V or Azure.

OVA (Option C):An export format, not a direct provisioning source for the Nutanix provider within Self-Service.

Therefore, ensuring anAHV Imageexists and is available on the cluster is the specific pre-configuration requirement for the Nutanix provider.

For users to successfully deploy Marketplace Blueprints to a specific infrastructure, the Project must have a configuredEnvironment.

The Gap:Merely adding the Account and whitelisting the Cluster in the Project settings (the "Infrastructure" tab) onlyauthorizesaccess. It does not tell the Self-Service enginehowto use that infrastructure (e.g., which Networks to attach, which Storage Containers to use, or what sizing policies to apply).

The Solution:The administrator must go to theEnvironmentstab within the Project andCreate a New Environmentmapped to the new Account and Cluster.

Marketplace Logic:Marketplace blueprints are typically "Environment Agnostic." When a user launches one, they are prompted to select a destination Environment. If no Environment exists for the new cluster, the user cannot select it as a target for deployment.