CLF-C02 Cloud Technology and Services 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 it's wrong here

  CloudFront, as a CDN, caches static and dynamic content at edge locations, so requests for cacheable objects return quickly, and for dynamic content it can use the AWS backbone to reach the origin. However, it requires DNS-based routing and does not provide fixed, globally anycasted static IP addresses for the application endpoint. It also adds an HTTP/HTTPS processing layer and is less suited for non-HTTP protocols (e.g., UDP gaming, VoIP) that Global Accelerator supports natively.

• ✓

  AWS Global Accelerator

  Why this is correct

  AWS Global Accelerator uses two global static anycast IP addresses at edge locations, where traffic enters the AWS network, then traverses the congestion-free AWS backbone directly to the configured endpoint(s). It seamlessly handles failover by rerouting to a healthy endpoint at the edge level within seconds. This reduces internet latency, jitter, and packet loss for TCP/UDP applications, and supports preserving the client's source IP for security and compliance.

• ✗

  Amazon Route 53 with latency routing

  Why it's wrong here

  Route 53 latency routing selects the DNS endpoint with the lowest measured latency from the user, but once the DNS response is returned, standard IP routing over the public internet carries the traffic to that endpoint. It cannot move traffic onto the AWS global network near the user; it only influences which regional endpoint receives the request. For applications needing consistent TCP/UDP performance, latency DNS still suffers from internet congestion, packet loss, and path variability beyond the first DNS lookup.

• ✗

  Amazon VPC peering

  Why it's wrong here

  VPC peering creates private, encrypted Layer 3 connectivity between two VPCs using AWS's backbone, which is excellent for inter-VPC communication, but it has no effect on how a user outside AWS reaches the application. Peering connections require explicit route table entries and do not offer any edge network entry points, anycast IPs, or global traffic acceleration. It solves east-west VPC connectivity, not the north-south problem of getting a distant user's packets efficiently into the AWS network.

Go deeper

Related to this question