AWS Certified SysOps Administrator – Associate — Question 275
A SysOps administrator is configuring Amazon CloudWatch alarms. A particular is constantly in the ALARM state.
What could be the reason for this issue?
Answer options
- A. Alarms continue to evaluate metrics against configured thresholds, even after they are triggered.
- B. After alarms are triggered, they remain in the ALARM state until they are manually disabled.
- C. After an alarm is triggered and an action is performed, the application logic must reset the alarm to its normal state.
- D. The alarm is not receiving appropriate metrics.
Correct answer: A
Explanation
Amazon CloudWatch alarms continuously evaluate the associated metric against the defined threshold for every evaluation period, regardless of whether the alarm has already been triggered. If the metric continues to breach the threshold, the alarm remains in the ALARM state. Alarms do not require manual intervention or application logic to reset, and a lack of metrics would typically result in an INSUFFICIENT_DATA state rather than a persistent ALARM state.