NCP-EUC · Question #54
An administrator has created a Prism Central Playbook Action named Virtual Desktop Add CPU to add 2 vCPU to virtual desktop when an alert is triggered after the virtual desktop's CPU usage has…
The correct answer is A. The virtual desktop CPU Usage alerts were not cleared. In Prism Central, Playbooks are event-driven and triggered by alert state changes - specifically when an alert is generated (transitions to active). If the initial CPU alert fires and adds vCPUs but the alert is never acknowledged or cleared, it remains in a persistent active…
Question
An administrator has created a Prism Central Playbook Action named Virtual Desktop Add CPU to add 2 vCPU to virtual desktop when an alert is triggered after the virtual desktop's CPU usage has exceeded 80%. Initially the Playbook Action works as expected, however over time it seems it is no longer being triggered. What is causing this issue?
Options
- AThe virtual desktop CPU Usage alerts were not cleared.
- BThe vNUMA boundary has been breached preventing more vCPUs to be added.
- CThere are no more CPUs availed to allocate to the VM.
- DAdditional vCPUs need to be registered.
How the community answered
(19 responses)- A95% (18)
- C5% (1)
Explanation
In Prism Central, Playbooks are event-driven and triggered by alert state changes - specifically when an alert is generated (transitions to active). If the initial CPU alert fires and adds vCPUs but the alert is never acknowledged or cleared, it remains in a persistent active state. Since the alert never transitions back to a resolved state and then re-triggers, the Playbook condition is never re-evaluated as a new event, and subsequent CPU spikes do not generate a new triggering alert. Clearing the alert resets the state machine so that the next threshold breach generates a fresh alert and re-triggers the Playbook. The vNUMA (B) and available CPUs (C) are plausible distractors but are not the root cause described.
Topics
Community Discussion
No community discussion yet for this question.