A city architect asks why putting a 311 portal in two Availability Zones improves resilience. What is the key engineering idea behind Availability Zones?
Select an answer to reveal the explanation.
Short Explanation
Picture two firehouses on opposite sides of town with separate utilities—if one loses power, the other still rolls. AWS designs AZs so they do not share single points of failure, which is why splitting a 311 portal across them actually helps. They are not the same building with a fancy name, and multi-AZ still is not a substitute for backups and DR planning.
Full Explanation
Each Availability Zone is designed with independent power, cooling, and networking so that a failure in one AZ is unlikely to take down another. That isolation is why multi-AZ architectures improve resilience for municipal workloads such as a 311 portal. AZs are distinct facilities within a Region, not cosmetic labels on one site. Multi-AZ high availability complements—but does not replace—backup and multi-Region disaster-recovery strategies.