Nutanix NCP-MCA Exam With Confidence Using Practice Dumps

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.

To create or configure aCustom Providerin Nutanix Self-Service (Calm), the administrator typically defines the provider's schema (endpoints, variables, and actions) using theSelf-Service DSL(Domain Specific Language) or by constructing a definition file.

YAML Definition:The standard workflow for creating complex custom providers involves defining the provider logic in Python (via the DSL) and compiling it into aYAMLfile, or writing the YAML definition directly.

Import/Update:This YAML file is then uploaded to the Self-Service interface to create or update the Provider definition. This allows the administrator to extend Self-Service capabilities to any infrastructure or service that has an API, beyond the native supported providers.

Note:While the question option phrasing ("Update the blueprint...") may be imprecise, the action of uploading aYAML fileis the specific mechanism associated with defining Custom Providers and DSL-based constructs in Nutanix Self-Service.

According to the Nutanix Prism Central Admin Guide, a category is a grouping of entities into key-value pairs. Categories are used to group entities (such as VMs, hosts, or subnets) based on specific criteria (e.g., Department: Marketing or Environment: Production).

Once entities are assigned to a category, administrators can link policies (such as security, protection, or automation playbooks) to the category rather than to individual entities. This allows for scalable and dynamic management, as any new entity tagged with that category will automatically inherit the associated policies.