A developer is launching a global application that delivers content to multiple countries. The developer needs to serve specific content based on the country of each user and each user's primary langu

Question

Options

• ACreate an Amazon API Gateway REST API. Create an AWS Global Accelerator standard
• BStore the content in a centralized Amazon S3 bucket. Enable S3 Transfer Acceleration on the
• CCreate an Amazon API Gateway REST API. Connect the REST API to AWS WAF. Use geo
• DConfigure an Amazon CloudFront distribution that uses the application as an origin. Configure the

• A
  15% (6)
• B
  10% (4)
• C
  5% (2)
• D
  71% (29)

Explanation

Option D is correct because Amazon CloudFront is AWS's Content Delivery Network (CDN) with 400+ global edge locations that cache and serve content close to users. CloudFront automatically exposes the CloudFront-Viewer-Country header and supports Accept-Language header forwarding, enabling Lambda@Edge or CloudFront Functions to route users to country- and language-specific content - all with low latency and high availability.

Why the distractors fail:

• A (API Gateway + Global Accelerator): Global Accelerator optimizes network routing using AWS's backbone but doesn't cache content at edge locations - it reduces network hops, not content delivery latency for diverse geo/language needs.
• B (S3 + Transfer Acceleration): S3 Transfer Acceleration speeds up uploads to S3, not content delivery to end users. It provides no geo-targeting or language-based routing capability.
• C (API Gateway + WAF geo-matching): WAF geo-matching is a security tool for blocking or allowing traffic by country, not for serving different content. API Gateway also has no built-in CDN caching, so global latency remains high.

Memory tip: When you see "global + low latency + content + geo-targeting," think CloudFront = CDN + Edge Caching + Viewer-Country headers. The key differentiator is that CloudFront caches at the edge while Global Accelerator only routes faster - caching wins for content delivery.

No community discussion yet for this question.