A company runs an internal browser-based application on EC2 instances behind an Application Load Balancer. The instances are in an Auto Scaling group across multiple Availability Zones. The group scales up to 20 instances during work hours and scales down to 2 instances overnight. Staff say the application is very slow at the start of the day, although it runs well by mid-morning. How should scaling be changed to address the complaints while keeping costs low?

The correct option is to implement a target tracking action triggered at a lower CPU threshold and decrease the cooldown period. Target tracking scaling policies are proactive and adjust capacity to maintain a specific metric (like CPU utilization) at a target value. By setting a lower CPU threshold, the Auto Scaling group will add instances sooner, anticipating increased demand. Decreasing the cooldown period allows the Auto Scaling group to respond more quickly to changes in demand, spinning up new instances faster when the office