An administrator has been notified of a critical alert associated with a VMware vCenter cloud account. The alert states that "Objects are not receiving data from adapter instance". The administrator…

Question

Options

• ASuspend
• BCancel Alert
• CRelease Ownership
• DDisable the alert in all polices

• A
  5% (1)
• B
  70% (14)
• C
  10% (2)
• D
  15% (3)

Explanation

Cancel Alert is correct because it clears the current triggered alert after the underlying issue has been resolved, signaling to the system that the problem no longer exists. Crucially, it leaves the alert definition active and enabled, so the alert will fire again if the same condition reoccurs in the future - exactly what the requirement describes.

• Suspend (A) is wrong because it temporarily silences the alert for a set duration, which means it won't notify you even if the problem comes back during that window - violating the "unless the problem occurs in the future" requirement.
• Release Ownership (C) is wrong because it simply un-assigns the alert from the administrator; it does nothing to clear or resolve the alert state.
• Disable the alert in all policies (D) is wrong because it permanently prevents the alert from ever firing again, even if the problem recurs - it removes the detection entirely rather than just closing the current instance.

Memory tip: Think of "Cancel Alert" like closing a resolved support ticket - you're marking this incident as done while keeping the monitoring rule alive, so any future recurrence opens a brand-new ticket automatically.

No community discussion yet for this question.