AWS Solutions Architect Associate (SAA-C03) · Free practice question 4 of 12
Scheduled scaling for predictable peaks
Traffic to the payroll portal at Kellerman Services rises sharply every weekday at 8:00 AM and falls at 6:00 PM, following the same pattern every week. Reactive scaling adds instances too slowly, so employees see slow responses in the first minutes of each morning. What should a solutions architect configure for the Auto Scaling group?
- A.A step scaling policy with a lower CPU alarm threshold
- B.A longer health check grace period
- C.Scheduled scaling actions that raise capacity shortly before 8:00 AM and lower it after 6:00 PM on weekdays
- D.A larger default instance warmup value
Show answer and explanation
Correct answer: C. Scheduled scaling actions that raise capacity shortly before 8:00 AM and lower it after 6:00 PM on weekdays
Why: Scheduled scaling changes capacity at specified times, so the group can scale out before a known daily surge instead of reacting to it. A lower alarm threshold still reacts after load begins, and health check grace periods and warmup settings affect how new instances are evaluated rather than when they are launched.
More free AWS Solutions Architect Associate (SAA-C03) questions
- IAM explicit deny overrides allow
- VPC Flow Logs for connectivity troubleshooting
- Transit Gateway instead of peering mesh
- RDS point-in-time restore
- Route 53 geolocation routing
- Data Lifecycle Manager for EBS snapshots
- DynamoDB Streams with Lambda
- Amazon MQ for broker migrations
- Graviton instances for price-performance
- Amazon Inspector vulnerability scanning
- Root user protection best practices