A parks department publishes static trail maps that visitors download worldwide. Which AWS capability best speeds delivery of that cached content?
Select an answer to reveal the explanation.
Short Explanation
Static maps love living at the edge—CloudFront edge locations stash copies close to hikers so they are not hauling every download from a far Region. That is the performance win for cached park maps. One lonely EC2 box or a tape shelf back home will not feel fast for a global audience.
Full Explanation
A parks department that publishes static trail maps downloaded by visitors worldwide should use Amazon CloudFront edge locations to cache those maps near users. CloudFront is the AWS content delivery network: it stores cacheable objects at edge locations so repeated downloads do not always travel back to the origin Region. For static maps, PDFs, and images, this reduces latency and origin load for tourists and residents far from the home Region.
Running a single large EC2 instance only in the farthest Region worsens global latency and creates a bottleneck. Storing maps solely in a private on-premises tape library blocks public download use cases. Disabling HTTPS to avoid TLS overhead is insecure and not an AWS performance best practice for public civic content.
Exam caveat: Static global content acceleration → CloudFront / edge locations. Do not confuse edge caching with Local Zones (latency-sensitive compute near metros) or with multi-Region origin HA, though they can combine.
Operational check: place maps in S3, front with CloudFront using Origin Access Control, set appropriate TTLs, enforce HTTPS, invalidate caches when trail data updates, and review cache-hit ratios so the parks team confirms worldwide visitors are mostly served from edges.