A citizen portal must handle lunchtime spikes and quiet nights. Leadership proposes one very large EC2 instance. What cost-and-elasticity guidance should the architect give?
Select an answer to reveal the explanation.
Short Explanation
One mega-server is a snowplow left idling in July—great at noon rush, wasteful at 2 a.m. Smaller instances behind Auto Scaling grow for the lunch spike and shrink when the portal naps.
Full Explanation
Horizontal scaling with Auto Scaling groups of smaller instances typically improves cost elasticity for variable public portals compared with a single oversized vertical instance. Reserved Dedicated Hosts and disabling scaling reduce flexibility. Client-side-only designs cannot replace required server-side APIs and security controls.