QuestionQ27

Validate Blueprints, Runbooks, Playbooks, and Automation Settings

An administrator has created a Self-Service Project that includes a blueprint to deploy a multi-tier application and a Playbook for post-deployment automation, such as tagging, monitoring configuration, and email notifications.

During testing, users report that the VMs deploy successfully, but the post-deployment automation tasks do not run as expected.

Which two actions should the administrator take to identify the cause of the issue?

Choose two
  • A Check the Playbook Execution History to verify if the Playbook was triggered and any tasks failed.
  • B Review the Audit Logs of the Prism Element cluster for VM creation timestamps.
  • C Verify that the Playbook is properly invoked by the correct blueprint action (e.g. Post-Deploy).
  • D Reassign the blueprint to a different Project and test deployment to rule out project-specific quota limits.
Explanation

Playbook Execution History determines whether the Playbook was triggered and identifies failed tasks. The blueprint must also invoke the Playbook through the appropriate action, such as Post-Deploy; otherwise, successful VM deployment does not start the post-deployment automation.

Community Discussion

No comments yet. Be the first to start the discussion!