A county must choose AWS Regions for a citizen portal where data-re…

Question

A county must choose AWS Regions for a citizen portal where data-residency rules constrain allowable locations and page-load latency for residents also matters. Which Region and AZ selection approach best balances these requirements?

Accepted Answer

Select Regions that satisfy residency and compliance constraints first, then prefer those with acceptable latency to the resident population and deploy across multiple Availability Zones in the chosen Region. — Residency rules are the fence line; latency is how long the drive feels inside the fence. Pick legal Regions first, then the ones that feel fast for citizens, and spread across AZs. Cheapest-anywhere or one lonely AZ ignores both compliance and resilience.

Answer

Always pick the globally lowest-price Region regardless of residency law or citizen latency.

Answer

Use a single Availability Zone in a non-compliant Region because multi-AZ is optional for public portals.

Answer

Place primary data only in Regions that violate residency rules if CloudFront is enabled in front of the portal.

A county must choose AWS Regions for a citizen portal where data-residency rules constrain allowable locations and page-load latency for residents also matters. Which Region and AZ selection approach best balances these requirements?

Short Explanation

Full Explanation