You want to deliver static content to users around the world with low latency. If you also want to reduce the number of requests to the origin, which service is the most appropriate?

Explanation

CloudFront caches content at edge locations and delivers it to users worldwide with low latency.

Per-choice explanations

Practical Use

Amazon CloudFront is a CDN service that caches content at edge locations distributed worldwide and responds from the nearest edge to the user. You can specify S3, ALB, API Gateway, or EC2 as origins. On the first request, content fetched from the origin is stored at the edge, and subsequent requests are served from the same edge. This delivers low-latency responses even to users outside the origin Region. It also reduces origin requests, lowering scaling requirements and cost on the origin side. In practice, a typical configuration is to use S3 as the origin for a static site and use Origin Access Control (OAC) to keep S3 private while serving only through CloudFront. For dynamic content, you can shorten the TTL or disable caching entirely and use only the benefits of TLS termination, WAF integration, gzip/brotli compression, HTTP/2, and HTTP/3. For custom logic at the edge, choose between CloudFront Functions (lightweight, JavaScript) and Lambda@Edge (general purpose, Node.js or Python). On SAA-C03, when keywords such as "deliver globally with low latency," "reduce origin load," or "cache static content" appear, CloudFront is the correct answer. Distractors include S3 Transfer Acceleration (whose primary use is upload acceleration, not download), Global Accelerator (anycast path optimization for arbitrary TCP/UDP, no caching), and Route 53 latency-based routing (DNS-level optimization without content caching).