Bird
0
0

You configured a CloudWatch alarm to trigger an Auto Scaling policy, but the instances are not scaling when the alarm state changes. What is the most likely cause?

medium📝 Debug Q14 of 15
AWS - CloudWatch
You configured a CloudWatch alarm to trigger an Auto Scaling policy, but the instances are not scaling when the alarm state changes. What is the most likely cause?
AThe EC2 instances are stopped
BThe SNS topic subscription is missing
CThe alarm threshold is set too low
DThe alarm's AlarmActions does not include the correct Auto Scaling policy ARN
Step-by-Step Solution
Solution:
  1. Step 1: Check AlarmActions configuration

    If the Auto Scaling policy ARN is missing or incorrect, the alarm cannot trigger scaling.
  2. Step 2: Rule out other options

    SNS subscription missing affects notifications, not scaling. Threshold too low triggers alarm but no scaling if policy missing. Stopped instances do not scale but alarm triggers still need correct action.
  3. Final Answer:

    The alarm's AlarmActions does not include the correct Auto Scaling policy ARN -> Option D
  4. Quick Check:

    Correct Auto Scaling ARN needed in AlarmActions [OK]
Quick Trick: Auto Scaling needs correct policy ARN in AlarmActions [OK]
Common Mistakes:
  • Confusing SNS subscription with scaling trigger
  • Ignoring ARN correctness
  • Assuming stopped instances auto scale

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes