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 systems into the scaling group without addressing the underlying policy issue will not stop the flapping and may lead to unnecessary resource consumption.

While a load balancer distributes traffic, its configuration is less likely to be the direct cause of the auto-scaling group itself repeatedly changing size based on metrics.

Rapid upsizing and downsizing, often called 'flapping' or 'thrashing,' is a classic symptom of an overly aggressive or poorly configured auto-scaling policy. This usually means the scaling thresholds are too close, or the cooldown periods are too short, causing the system to react repeatedly to minor fluctuations. Reviewing and adjusting these policies, such as the thresholds, cooldown periods, or aggregation types, is the immediate next step to stabilize the application's resource allocation and prevent unnecessary resource consumption or performance instability.

Monitoring for another 24 hours without investigation prolongs the issue, potentially leading to continued performance instability or increased costs.