NCP-MCA practice question 6 of 25

An administrator created a Self-Service Project, including a blueprint that deploys a multi-tier application and a Playbook to perform…

An administrator created a Self-Service Project, including a blueprint that deploys a multi-tier application and a Playbook to perform post-deployment automation (e.g., tagging, monitoring setup, and email notifications). However, during testing, users report that while the VMs are successfully deployed, the post- deployment automation tasks are not executing as expected. Which two steps should the administrator take to determine the cause of the issue? (Choose two.)

Answer options

A: Reassign the blueprint to a different Project and test deployment to rule out project-specific quota limits.

B: Review the Audit Logs of the Prism Element cluster for VM creation timestamps.

C: Check the Playbook Execution History to verify if the Playbook was triggered and any tasks failed. Correct answer

D: Verify that the Playbook is properly invoked by the correct blueprint action (e.g., Post-Deploy). Correct answer

Correct Answer:

C. Check the Playbook Execution History to verify if the Playbook was triggered and any tasks failed.; D. Verify that the Playbook is properly invoked by the correct blueprint action (e.g., Post-Deploy).

Explanation

If VMs build but automation does not run, first confirm whether the playbook actually fired and, if so, which task failed. Playbook Execution History (menu: Operations → Playbooks → History) records every trigger, status, and error log, allowing root-cause inspection. If no execution is recorded, the next step is to confirm the blueprint really invokes the playbook through the Post-Deploy (or other) action mapping. A mis-configured or missing action binding will prevent the playbook from launching even though the VM portion of the blueprint completes successfully.

Why Incorrect

A. Project quota affects VM provisioning, not post-deploy playbook invocation; VMs are already building, so quota is not the issue.
B. Prism Element audit logs only show VM operations; they contain no playbook trigger or task data, thus provide little insight into automation failure.

References

1. Nutanix Prism Central Admin Guide 6.10, “Working with Playbooks → Viewing Execution History”, pp. 325-326 – describes checking trigger and task status for troubleshooting.

2. Nutanix Calm 6.10 Guide, “Blueprint Actions and Playbook Mapping → Post-Deploy Actions”, pp. 112-114 – explains configuring a blueprint to call a playbook after deployment and effects of misconfiguration.

3. Nutanix University Courseware, NCP-MCA 6.10 “Module 5: Automation”, slide 39 – recommends verifying playbook binding and reviewing execution history as first steps in troubleshooting SSP automation.

Keep practicing

Take the free NCP-MCA practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test