You set up a CloudWatch alarm to monitor disk read operations with a threshold of 5000, but the alarm never enters ALARM state even though the metric exceeds 6000. What is the most probable reason?

medium📝 Debug Q6 of 15

AWS - CloudWatch

AThe alarm's EvaluationPeriods is set to 3, but the metric only breached the threshold once.

BThe alarm's ComparisonOperator is set to LessThanThreshold instead of GreaterThanThreshold.

CThe alarm's metric namespace is incorrect, so it is monitoring a different metric.

DThe alarm's period is set to 60 seconds, which is too short for the metric.

Step-by-Step Solution

Solution:

Step 1: Check EvaluationPeriods
If EvaluationPeriods is 3, the metric must breach the threshold for 3 consecutive periods to enter ALARM.
Step 2: Analyze metric breaches
The metric only exceeded the threshold once, so the alarm stays in OK state.
Final Answer:
EvaluationPeriods requires multiple breaches; single breach insufficient -> Option A
Quick Check:
EvaluationPeriods controls consecutive breaches needed [OK]

Quick Trick: EvaluationPeriods requires consecutive breaches to trigger ALARM [OK]

Common Mistakes:

MISTAKES

Ignoring EvaluationPeriods setting
Assuming single breach triggers alarm immediately
Confusing ComparisonOperator impact with EvaluationPeriods

Master "CloudWatch" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More AWS Quizzes

You set up a CloudWatch alarm to monitor disk read operations with a threshold of 5000, but the alarm never enters ALARM state even though the metric exceeds 6000. What is the most probable reason?

Step 1: Check EvaluationPeriods

Step 2: Analyze metric breaches

Final Answer:

Quick Check:

Want More Practice?