A city tax portal sees seasonal filing spikes and runs a stateless EC2 web fleet behind a load balancer. How should compute scale to meet request demand?
Select an answer to reveal the explanation.
Short Explanation
Tax season is a crowd at the counter—you open more windows when the line grows. Auto Scaling on request-count (or similar demand metrics) grows and shrinks the EC2 web fleet with the load balancer. One yearly vertical bump, killing the LB, or shrinking with Spot interruptions at peak is how you create a citizen outage.
Full Explanation
EC2 Auto Scaling adjusts fleet capacity using metrics such as request count or CPU so a stateless web tier can meet elastic demand. For seasonal municipal tax filing, scaling out horizontally behind a load balancer is the associate high-performing compute pattern. Static vertical sizing, removing load balancing, or deliberately reducing capacity at peak undermines elasticity and availability.