Coastal residents report high latency to a single inland Region hosting a permit portal. What multi-Region reason best addresses that user experience?
Select an answer to reveal the explanation.
Short Explanation
Distance still matters—bits crawling across a continent feel sluggish on a permit form. Standing up a second Region nearer the coast is a classic reason to go multi-Region for lower end-user latency. One AZ, Glacier cold storage, or hard-coded IPs will not fix round-trip time for those coastal users.
Full Explanation
Placing application endpoints in Regions geographically closer to users can reduce latency and improve interactive experience. Multi-Region designs are therefore used not only for disaster recovery but also for performance. Consolidating into a single AZ or archival storage does not address client-to-Region network distance. CLF-level guidance emphasizes matching Region placement to latency-sensitive citizen workloads when requirements justify it.