Bird
0
0

A CloudWatch alarm is not triggering despite high CPU usage. What is a common misconfiguration to check?

medium📝 Debug Q7 of 15
AWS - CloudWatch
A CloudWatch alarm is not triggering despite high CPU usage. What is a common misconfiguration to check?
AThe metric unit is set to Bytes instead of Percent
BThe alarm threshold is set too high
CThe alarm is set to OK state manually
DThe metric namespace is misspelled
Step-by-Step Solution
Solution:

  1. Step 1: Review Alarm Threshold

    If threshold is higher than actual CPU usage, alarm won't trigger.

  2. Step 2: Check Other Options

    Namespace misspelling causes no data; manual state change is rare; unit mismatch causes errors but less common.

  3. Final Answer:

    The alarm threshold is set too high -> Option B

  4. Quick Check:

    Threshold too high prevents alarm trigger [OK]
Quick Trick: Set alarm threshold below expected metric to trigger [OK]
Common Mistakes:
MISTAKES
  • Ignoring threshold value
  • Assuming manual state changes
  • Confusing units

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
API Gateway - Lambda integration - Quiz 10hard API Gateway - Why API Gateway matters - Quiz 4medium API Gateway - REST API creation - Quiz 13medium API Gateway - API keys and usage plans - Quiz 1easy AWS Lambda - Lambda execution model - Quiz 4medium Auto Scaling - Scaling policies (target tracking, step, simple) - Quiz 7medium CloudWatch - Log groups and log streams - Quiz 7medium DynamoDB - Scan vs query performance - Quiz 8hard RDS and Relational Databases - Launching an RDS instance - Quiz 11easy SNS and SQS - SNS notification types (email, SMS, Lambda) - Quiz 11easy