Seasonal tax-deadline traffic spikes overwhelm a city’s web tier that today only upsizes to larger instance types. What scaling approach should the architect prefer for elasticity?
Select an answer to reveal the explanation.
Short Explanation
Tax season is like parade day—you want more street lanes, not one giant truck. Horizontal Auto Scaling adds instances when metrics climb and sheds them afterward. Sitting on one forever-huge box or hoping a reboot fixes overload misses the elasticity play.
Full Explanation
Horizontal scaling with Auto Scaling groups adds capacity by launching additional instances in response to metrics such as CPU or request count, then scales in when demand falls. That pattern fits seasonal municipal workloads better than permanent vertical upsizing of a single host. Concentrating in one AZ or relying on reboots does not provide elastic, fault-tolerant scale-out.