SOA-C02 Networking and Content Delivery Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Amazon CloudFront

  Why this is correct

  Amazon CloudFront is a content delivery network (CDN) that caches static assets, such as HTML, CSS, JavaScript, and images, at edge locations geographically close to users. When a user requests a file, CloudFront serves it from the cache if the TTL has not expired, drastically reducing latency and offloading repeated requests from the underlying EC2 instances. It can be configured with an Application Load Balancer or EC2 as the origin and automatically handles SSL termination, HTTP/2, and compression, making it the ideal choice for static website acceleration.

• ✗

  AWS Global Accelerator

  Why it's wrong here

  AWS Global Accelerator uses the AWS global network and static anycast IP addresses to route user traffic to the nearest edge location, improving connection reliability and reducing jitter for TCP/UDP traffic. However, it does not cache content at the edge; every request is still forwarded to the configured origin resources, such as an Application Load Balancer or EC2 instances. This means it cannot reduce origin load for static content or serve cached responses, so it is not a substitute for CloudFront in this scenario.

• ✗

  AWS Direct Connect

  Why it's wrong here

  AWS Direct Connect establishes a dedicated, private, high-bandwidth network connection between an on-premises data center and AWS, bypassing the public internet. While it reduces network latency and jitter for hybrid cloud traffic, it offers no caching capability and is not designed to distribute content to end users over the internet. Even if a company manages its own infrastructure, Direct Connect would not improve website latency for global consumers or offload object requests from EC2 instances, making it irrelevant for a static website fronted by a CDN.

• ✗

  Amazon Route 53

  Why it's wrong here

  Amazon Route 53 is a scalable and highly available Domain Name System (DNS) service that resolves human-readable domain names into IP addresses and supports advanced routing policies like latency-based, geolocation, weighted, and failover routing. However, DNS servers resolve queries to the appropriate endpoint (e.g., an ALB or CloudFront distribution) and do not store or cache actual web content. Route 53 may influence where users land, but it cannot serve cached HTML or images, so it fails to address the need for content caching and origin offloading for a static website.

Go deeper

Related to this question