A metro transit agency needs ultra-low latency compute for XR kiosks in the downtown core, closer than the parent Region. Which AWS construct is designed for that purpose?
Select an answer to reveal the explanation.
Short Explanation
Local Zones pull a slice of AWS compute closer to a big metro so XR kiosks are not waiting on a distant Regional data center. That is the ultra-low-latency story for downtown. Edge caches are great for static content, not a full swap-in for those low-latency compute needs.
Full Explanation
AWS Local Zones place select AWS services closer to large population centers to support latency-sensitive workloads. Municipal XR or interactive kiosk scenarios are common CLF illustrations of why Local Zones exist relative to a parent Region. They differ from CloudFront edge caching, which primarily distributes content rather than hosting full Regional service footprints. Candidates should identify Local Zones as metro-proximate extensions, not archival or third-party substitutes.