During unpredictable flash-sale promotions, an e-commerce company sees CPU utilization across its web-tier instances climb above 80 percent within minutes. The operations team wants the environment to add or remove compute instances automatically whenever a monitoring metric crosses a defined threshold, without relying on a fixed schedule. Which scaling method should they implement?
Configure a recurring scaling schedule
Manually resize instances during each promotion
Enable metric-based automatic scaling
Replace application servers with larger instance types only
Metric-based (dynamic) autoscaling monitors cloud metrics such as CPU or request count and automatically launches or terminates instances when the metric rises above or falls below the configured threshold, delivering rapid elasticity for unplanned spikes. Scheduled or manual actions require knowing demand in advance, and merely resizing to larger instance types adds capacity only once and will not respond to future peaks.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is metric-based scaling?
Open an interactive chat with Bash
How does metric-based scaling differ from scheduled scaling?
Open an interactive chat with Bash
What are the key benefits of metric-based autoscaling?