In the Nutanix Self-Service (Calm) Blueprint lifecycle, tasks are executed in a specific order relative to the provisioning of the infrastructure (Substrate).
* Pre-Create Task:This is the specific phase designed to run scripts or set variablesbeforethe VM provision call is sent to the provider (AHV).
* Workflow:
* The developer creates a pre-create task (e.g., a Python script) to generate the custom hostname string based on logic (e.g., date, user input, or sequence).
* The script outputs this string to a variable (e.g., @@{vm_hostname}@@).
* The VM Service configuration (Substrate) references this variable in the "VM Name" or
"Hostname" field.
* Execution:When the blueprint launches, the pre-create task runs first, populates the variable, and then the VM creation occurs using that calculated name.
* Tasks in post-create or package-install (Options B and C) runafterthe VM has already been provisioned and named, making them too late for this requirement.

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.

Playbooks are a feature of Intelligent Operations (formerly Prism Pro or X-Play), not Nutanix Self-Service (formerly Calm). Therefore, the first step is always to access the Intelligent Operations console in Prism Central.
The logical flow for defining an automation routine in a Playbook isTrigger first, then Action.
* Select Trigger:The administrator must first definewhenthe playbook runs (e.g., on an Alert, an Event, or Manually).
* Add Actions:Once the trigger is established, the administrator defineswhathappens (e.g., Power off VM, Send Email, Slack Notification).
The correct order found in the Nutanix Intelligent Operations Guide is: Access Intelligent Operations > Create Playbook > Select Trigger > Add Actions > Save.

When a Playbook fails to fire despite an Alert occurring, the most common and "likely" cause is a mismatch in theTriggerconfiguration logic.
* Trigger Precision:X-Play Triggers are precise. If the administrator selected theAlerttrigger, they must select asingle specificAlert Policy (e.g., "Host High Memory"). If the high-severity alert that occurred was "VM High Memory" (a different policy), the Playbook will not trigger, even if both are "High Severity."
* Alerts Matching Criteria:To coverallhigh-severity alerts, the administrator must use theAlerts Matching Criteriatrigger and filter by Severity == Critical. If they used the specific "Alert" trigger or configured the criteria incorrectly (e.g., wrong entity type), the system is "working as implemented" (ignoring non-matching events), but the logic does not match the user's intent.
* Autopilot (Option C):While X-Play has an Autopilot feature for KPI optimization, it is not a mandatory requirement for standard alert-based remediation playbooks to function.
The image typically shows the distinction between the "Alert" trigger (Select one policy) and "Alerts Matching Criteria" trigger (Select filters like Severity/Entity), illustrating how a configuration error here leads to the issue described in Question 40.

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.