To automate the provisioning of a VM and the subsequent application installation within a Nutanix Self-Service (Calm) Blueprint, the administrator must configure a Service.

The definition of a Service in a blueprint involves three distinct components to achieve this requirement:

VM Resource: Configuring the underlying infrastructure specifications (vCPUs, Memory, Disks).

Guest Customization: Configuring Cloud-init (Linux) or Sysprep (Windows) to handle the initial OS bootstrap (hostname, user creation).

Tasks (Package Install): Adding a script task (e.g., Shell or PowerShell) under the "Service Installation" action or a dedicated Package install step. This task executes after the VM is provisioned and running to install the web server application.

To enforce different configurations for different types of workloads within the same Project, Nutanix Self-Service uses Environments .

Environments: These are logical configurations within a Project that map to specific infrastructure settings. An administrator can define multiple environments (e.g., "Development" and "Production") within the "Engineering" project.

Category Assignment: Within each Environment configuration, the administrator can define specific VM Categories that will be automatically applied to any VM provisioned into that environment.

Mapping:

Production Environment: Assign the category Protection: async_1hr_repl (Matches requirement: Asynchronous remote replication every 1 hour).

Development Environment: Assign the category Protection: snap_24_hr (Matches requirement: Daily snapshots).

Execution: When a user launches a blueprint, they select the target Environment (Dev or Prod). The system automatically tags the VMs with the categories defined in that environment, which in turn engages the Protection Policies associated with those tags.

Option B uses the wrong category values (sync_remote_repl instead of async). Options C and D suggest using Playbooks, but the native and most efficient method for applying deployment-time governance in Self-Service is via the Project Environment settings.

To automate actions based on a signal from a third-party monitoring tool, the administrator should use the Webhook Trigger in Nutanix Intelligent Operations (X-Play).

Webhook Trigger: The administrator creates a playbook that starts with a Webhook Trigger. This generates a unique URL.

Integration: The third-party tool is configured to send an HTTP POST request (the notification) to this unique URL when the "low capacity" threshold is reached.

Automation: Receiving this signal automatically triggers the playbook to execute the expansion tasks (e.g., calling APIs to provision more VDI nodes or expand storage), removing the manual step.

While "Alert" (Option D) is used for native Nutanix alerts, the "Webhook" is the designated mechanism for receiving external events.

In Nutanix Self-Service (Calm), the Marketplace Manager is the specific administrative view used to govern the publication of blueprints.

When a developer submits a blueprint for publication, it enters a "Pending Approval" state. An administrator must access the Marketplace Manager , navigate to the Approval Pending tab, and explicitly approve the blueprint. Only after this approval does the blueprint become visible to end-users in the standard Marketplace.

"Approval Policies" (Option C) refer to runtime restrictions (e.g., requiring approval to provision a VM), not the pre-publication governance of the blueprint design itself.

The Library in Nutanix Self-Service (formerly Calm) serves as a central repository for reusable automation assets that can be shared across multiple Blueprints and Projects. According to the Self-Service Administration Guide, the Library specifically contains:

Tasks (Scripts): The "Task Library" allows administrators to save Shell, PowerShell, Python (eScript), or HTTP tasks. These published tasks can then be imported into any blueprint, ensuring code reusability and standardization.

Variable Types (Variables): The Library also hosts Variable Types (often simply referred to as user-defined variables in the context of the library). Administrators can create and save complex variable definitions (such as lists or static values) in the Library to be reused in different blueprints without redefining them every time.

Endpoints (Option C) are configured in the global Settings or Project settings, not within the Library tab. Apps and Blueprints (Options A and D) have their own dedicated "Apps" and "Blueprints" tabs in the navigation bar.

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 efficiently identify the source Blueprint for every VM created during a test, the administrator should utilize the built-in Blueprint Name Macro within a Multi-VM structure.

Macro Usage: The macro @@{calm_blueprint_name}@@ automatically resolves to the name of the blueprint being deployed (e.g., "Test_BP_Version_A").

Efficiency: By using a Multi-VM blueprint (which creates all four VMs in one deployment action) and configuring the VM Name field in the service definition to include this macro (e.g., VM-@@{calm_blueprint_name}@@-@@{calm_array_index}@@), the administrator ensures that every resulting VM is automatically tagged with its source blueprint name in the hypervisor (Prism Element/Central) list.

Why not others:

Option A involves "Single VM Blueprint" and "cloning," which is a manual or secondary process that is less efficient than a native Multi-VM definition.

Option C uses @@{calm_application_name}@@, which identifies the specific instance (e.g., "App-1"), not the blueprint design (e.g., "Web-Server-v2") that is being tested.

In Nutanix Self-Service (formerly Calm), Macros are used to reference variables within scripts, task definitions, and configurations. The documented syntax for all macros requires the variable name to be enclosed within double "at" symbols and curly braces.

Syntax: @@{variable_name}@@

Usage: This format is used for both user-defined variables (e.g., @@{db_password}@@) and built-in system macros (e.g., @@{address}@@, @@{calm_time}@@, @@{calm_project_name}@@).

Evaluation: When the Self-Service engine executes a task, it parses the string, identifies the pattern @@{...}@@, and substitutes it with the actual value of the variable from the current context before sending the script to the target machine.

Nutanix Disaster Recovery uses Protection Policies to automate replication. These policies are applied to VMs dynamically based on Categories . To protect every VM from both blueprints described, the administrator must select a category that is common to both sets 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 from either blueprint 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).

When troubleshooting or optimizing blueprints where complex operations (like Provisioning combined with detailed Network Configuration) frequently fail, the recommended best practice is to split the steps into smaller tasks.

In Nutanix Self-Service (Calm), the Audit tab provides a sequential log of every task executed during an application's lifecycle. If provisioning and network configuration are bundled into a "single step" (e.g., a large script or a single package install), a failure makes it difficult to determine if the issue was with the VM creation, the OS boot, or the specific network parameter application.

By splitting the logic into distinct tasks (e.g., Task 1: Provision VM, Task 2: Configure Network), the administrator can:

Isolate the failure: The Audit log will clearly show "Provision VM: Success" and "Configure Network: Failed".

Validate inputs: It ensures the VM is fully available before attempting configuration.

Improve Auditing: Granular logs allow for faster root cause analysis of the "misconfigured parameters."

Retrying (Option B) or adding delays (Option D) are reactive measures that do not address the root cause of configuration errors, and disabling logging (Option C) hinders troubleshooting.