A museum photo site serves the same images to viewers worldwide, and the images rarely change. A teammate wants Global Accelerator in front of the origin so those images are cached near viewers. Which design caches the images at the edge?
Select an answer to reveal the explanation.
Short Explanation
You asked for a library that keeps copies near every town, and someone offered a faster highway instead. Global Accelerator improves the path and does not store your images, so the cache you want is CloudFront. A quicker route to one origin still fetches the object every time.
Full Explanation
CloudFront stores cacheable objects at edge locations and answers later viewers from that cache, which is the right fit for images that rarely change. Global Accelerator gives the origin static anycast addresses and carries packets over the AWS network to a healthy regional endpoint. It does not keep a copy of an object for the next viewer. A latency-based DNS record only chooses where the name resolves. The bytes still come from the origin on every request. Transfer Acceleration uses the edge network to speed a transfer to or from S3. It does not build a shared content cache that serves the same image to many viewers. Caveat: the distribution still needs a cache policy that allows these image paths to be stored, and a viewer cookie or query string that is unique per request will fragment that cache. Operational check: request the same image twice from a viewer far from the origin and confirm the second response is served from CloudFront while the origin request count for that object stays flat.