Where must an automated action be enabled before it can be initiated by a triggered alarm?

Question

Options

• AObject's associated policy
• BObject's associated recommendation
• CObject in the default policy
• DObject's associated symptom definition

• A
  87% (40)
• B
  7% (3)
• C
  2% (1)
• D
  4% (2)

Explanation

Option A is correct because, in VMware Aria Operations (vROps), automated actions are governed by policies - the central control plane for monitoring behavior. An automated action must be explicitly enabled within the policy associated with the target object before the system will execute it when an alarm fires, even if the action itself is defined elsewhere.

Why the distractors are wrong:

• B (Recommendation): Recommendations are advisory suggestions surfaced in alerts to guide manual remediation; they do not control whether an action runs automatically.
• C (Default policy): The action must be enabled in the policy associated with that specific object, not necessarily the default policy - objects can inherit different policies.
• D (Symptom definition): Symptom definitions specify the conditions that contribute to an alert, not the authorization or enablement of actions.

Memory tip: Think of a policy as a permission slip - even if an automated action exists and an alarm fires, the action won't run without that slip being signed (enabled) in the object's governing policy.

No community discussion yet for this question.