Bird
0
0

You configured a step scaling policy but it never triggers scaling actions even when the metric crosses thresholds. What is the most likely cause?

medium📝 Debug Q14 of 15
AWS - Auto Scaling
You configured a step scaling policy but it never triggers scaling actions even when the metric crosses thresholds. What is the most likely cause?
AThe scaling adjustment values are negative
BThe metric alarms are not properly linked to the scaling policy
CThe target tracking policy is overriding the step scaling policy
DThe Auto Scaling group has no instances
Step-by-Step Solution
Solution:
  1. Step 1: Check alarm linkage

    Step scaling policies rely on CloudWatch alarms to trigger. If alarms are not linked, no scaling occurs.
  2. Step 2: Evaluate other options

    Target tracking does not override step scaling; negative adjustments cause scale-in, not no action; no instances means no scaling needed.
  3. Final Answer:

    The metric alarms are not properly linked to the scaling policy -> Option B
  4. Quick Check:

    Missing alarm linkage = no scaling trigger [OK]
Quick Trick: Step scaling needs alarms linked to trigger [OK]
Common Mistakes:
  • Assuming target tracking disables step scaling
  • Ignoring alarm configuration
  • Confusing negative adjustment with no scaling

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes