While reviewing the auto-scaling events for a web application, a cloud engineer identified that the application upsized and downsized multiple times within the last hour. Which of the following…

Adding more instances to the scaling group does not address the root cause of thrashing and may increase costs without resolving the flapping behavior.

Load balancer configuration governs traffic distribution across existing instances, not the triggers that initiate scaling events, so it is not the source of this problem.

When an application scales up and down multiple times within an hour, it is exhibiting scaling thrash, which is typically caused by policy misconfiguration - for example, scale-out and scale-in thresholds set too close together, or an insufficient cooldown period that allows the next trigger to fire before the fleet stabilizes. Reviewing and correcting the policies is the immediate and most effective remediation step.

Monitoring for an additional 24 hours delays remediation when the likely cause - policy misconfiguration - can be investigated and corrected immediately.