SOA-C03 · Question #128
An application runs on Amazon EC2 instances behind an Application Load Balancer (ALB). The application takes up to 2 minutes to populate a local cache after the application is started. The…
The correct answer is A. Change the slow_start.duration_seconds target group attribute to 120 seconds. Before rebooting. The slow start feature of an ALB target group (slow_start.duration_seconds) is specifically designed to let new or newly healthy targets ramp up gradually, giving them a smaller, increasing share of traffic over a defined period. Setting it to 120 seconds allows each instance…
Question
An application runs on Amazon EC2 instances behind an Application Load Balancer (ALB). The application takes up to 2 minutes to populate a local cache after the application is started. The application reports as healthy in the target group health check a few seconds after starting. A CloudOps engineer observes that after some of the instances are rebooted, the instances receive an equal share of the traffic immediately after each instance reports as healthy. The application needs to receive a gradually increasing share of the traffic while the application cache is populated. Which solution will meet this requirement?
Options
- AChange the slow_start.duration_seconds target group attribute to 120 seconds. Before rebooting
- BChange the HealthCheckTimeoutSeconds paramotor in the target group to 120 seconds. Before
- CConfigure an Amazon CloudWatch alarm to monitor the health check status. Configure the action
- DCreate an Amazon EC2 Auto Scaling group. Attach the existing EC2 instances to the Auto
How the community answered
(53 responses)- A81% (43)
- B9% (5)
- C6% (3)
- D4% (2)
Explanation
The slow start feature of an ALB target group (slow_start.duration_seconds) is specifically designed to let new or newly healthy targets ramp up gradually, giving them a smaller, increasing share of traffic over a defined period. Setting it to 120 seconds allows each instance to warm its local cache during that time instead of receiving a full share of requests immediately, which matches the 2-minute cache warm-up requirement.
Topics
Community Discussion
No community discussion yet for this question.