An operations team wants an Auto Scaling group to add one instance when average CPU exceeds 70% but add four instances at once when average CPU exceeds 90%, using one policy attached to one CloudWatch alarm. Which scaling policy type can respond this way?
Choose one.
Step scaling sizes the capacity adjustment to how far the metric breached the alarm threshold, using step adjustments you define.
Only step scaling lets you say 'a small breach adds one instance, a large breach adds four' — the adjustment scales with breach magnitude. Target tracking holds one value and hides its alarms; simple scaling makes exactly one fixed adjustment per cooldown; scheduled scaling ignores metrics entirely.
- Identify the requirement: different response sizes at different severity levels of the same metric.
- Create a CloudWatch alarm on average CPU for the Auto Scaling group.
- Attach a step scaling policy with step adjustments: +1 instance for the 70–90% band, +4 instances above 90%.
- Configure instance warmup so newly launched instances are counted correctly during multi-step responses.
Exam tip: Adjustments sized to how far the alarm is breached are the signature use case for step scaling.
Auto Scaling and Elasticity: EC2, Caching, and Database Scaling — the lesson that teaches this.