An administrator is configuring a new Self-Service project. There is a Playbook targeting VMs with the respective CalmProject category that automates…

To be certain that both the Self-Service project scoping and the post-deployment Playbook work, the administrator should:

• first manually fire the Playbook with “Execute on Behalf Of”, selecting a VM that carries the CalmProject category. This runs every task exactly as the Playbook would when it is later triggered automatically, validating its logic and variable resolution.

• then deploy the blueprint from inside the same Project. The resulting VM(s) inherit the CalmProject category, so the Playbook should trigger automatically; observing this confirms that the Project/blueprint binding and Playbook trigger are correctly configured before opening access to users.

A. “Execute” lacks entity context; tasks that depend on VM-level variables or categories will not be validated.

C. Deploying the Marketplace-level blueprint bypasses the Project context; VMs will not receive the Project category, so the Playbook trigger cannot be confirmed.

1. Nutanix Prism Central Guide v2023.1, “Testing Playbooks – Execute vs. Execute on Behalf Of”, p.228-229, paras 3-5.

2. Nutanix Calm & Self-Service Admin Guide v6.5, “Project Categories and Playbook Triggers”, p.114-116.

3. Nutanix Calm Self-Service Admin Guide v6.5, “Validating a Project: Deploying a Blueprint from the Assigned Project”, p.120.

4. Nutanix University NCP-MCA v6.5 Courseware, Module 6 “Playbooks”, slides 27-30.