A city’s citizen portal Auto Scaling group currently registers targets in only one Availability Zone behind an Application Load Balancer. Leadership wants production-grade high availability. What should the architect change?
Select an answer to reveal the explanation.
Short Explanation
One AZ behind a load balancer is still a single neighborhood going dark. Spread the ASG across two or more AZs so the ALB has healthy targets when one zone hiccups. Bigger boxes in one zone do not buy AZ isolation.
Full Explanation
Production web tiers should place Auto Scaling capacity in at least two Availability Zones and use a multi-AZ Application Load Balancer so traffic can shift when an AZ fails. Pinning targets to one AZ creates an Availability Zone single point of failure despite the ALB. Replacing the ALB with a single reverse proxy or disabling health checks further concentrates risk. Multi-AZ spread is a core SAA high-availability pattern for municipal portals.