Nutanix Playbooks (part of Prism Central Automation) support multiple trigger types—Alert, Event, Webhook—and each trigger defines how automation workflows begin. The Nutanix Automation documentation highlights the following key rules:
1. Event Triggers (Correct Answer)
Playbooks using anEventtrigger supportmultiple playbook tasks, including script tasks, VM power operations, Prism actions, and more.
Nutanix documents specify that:
Event-based Playbooks activate when specificPC or cluster eventsoccur.
After an event trigger fires, administrators may definemultiple sequential actionsinside the Playbook.
This allows complex automation chains such as remediation actions, notification flows, or branching logic.
Therefore,Option D is correct, because Event-triggered Playbooks allow multiple actions to be added.
Why the other options are incorrect
❌Option A — Alert Trigger
Alert triggers only allowone alert definition per Playbook trigger.
Nutanix documentation states that an Alert trigger is mapped toa single alert policy, not multiple alerts.
Thus, Option A is incorrect.
❌Option B — Branch Step
ABranchisnot a trigger; it is aflow control elementusedafterthe Playbook has already started.
Branch steps define conditional paths but do not permit the addition of multiple "actions" as a trigger.
Therefore, Option B is incorrect.
❌Option C — Webhook Trigger
Webhook-triggered Playbooks start when external systems send an HTTP POST request.
While the Playbook may contain multiple tasks after triggering, the question specifically refers to addingmultiple scriptable tasks as part of the trigger, which is not possible.
Webhook triggers acceptonly one incoming webhook definition, not multiple script tasks embedded in the trigger.
Thus, Option C is incorrect.
