The only way to prove that the self-service Project mapping, the blueprint, and the post-deployment Playbook all interact correctly is to launch (test-deploy) the blueprint inside the Project and then view the Playbook execution status. This single action validates

1) that the Project’s credential, quota, and network mappings allow a deployment, and

2) that the Playbook is automatically triggered by the post-deploy task and completes successfully.

Running the Playbook by itself or reviewing cluster tasks does not confirm the end-to-end workflow that users will invoke.

A. Running the Playbook alone never tests blueprint triggers or Project resource mappings; it validates only the Playbook logic in isolation.

B. Prism Element task history records cluster operations, not Calm/X-Play execution; it cannot confirm Playbook trigger or success.

C. Moving the blueprint to another Project changes the environment and still requires a test deploy; comparison of usage offers no functional validation.

1. Nutanix Calm Administration Guide 3.6, “Creating and Testing Blueprints” pp. 138-140: “Use Test Deploy to launch the blueprint in its Project and verify post-deployment runbook execution before publishing.”

2. Nutanix Prism Central Admin Guide pc.2023.3, Chapter “Playbooks – Viewing Execution History”, p. 421: “After a blueprint deploy triggers a post-deployment Playbook, its status appears in Playbooks > History.”

3. Nutanix University Courseware “NCP-MCA v6.10: Automation and Orchestration”, Module 4, Slide 27: “Best practice—perform a test deployment of the blueprint to confirm Project mappings and Playbook execution prior to enabling self-service.”