A county elections office is deploying a voter-results API and needs high availability within one AWS Region. What design choice best meets that goal?
Select an answer to reveal the explanation.
Short Explanation
Think of Availability Zones like separate power grids in the same city—if one goes dark, the other can still serve results night. Spreading the voter-results API across at least two AZs in the Region is how you get high availability without leaving the Region. One AZ or one giant box is a single point of failure; edge cache alone is not your API compute.
Full Explanation
AWS Availability Zones are isolated locations within a Region. Deploying an application across multiple AZs reduces the impact of an AZ-level disruption and is a foundational high-availability pattern. For a civic voter-results API that must stay available during election night, multi-AZ placement within the chosen Region is the appropriate CLF-level control. Edge locations and single-AZ designs do not replace multi-AZ Regional architecture for primary application availability.