CloudFront vs Global Accelerator vs Route 53 for SAA-C03: What Each One Does
Know this topic? Test it on a full SAA-C03 paper
A complete SAA-C03 practice exam: 65 questions in 130 minutes, an explanation on every item and an Exam Coach report that ranks your weakest domains.
AWS-SAA-FULL
Try a free AWS SAA exam
Already have an account? Log in to redeem
CloudFront caches content at edge locations. Global Accelerator gives you static anycast IPs and carries TCP or UDP traffic over the AWS network, without caching. Route 53 is DNS, with routing policies for latency, failover, weighting and location. Choose by what the requirement describes: content, network path or name resolution.Checked against AWS's published exam guide on 9 November 2026.
In this guide
The three at a glance
| CloudFront | Global Accelerator | Route 53 | |
|---|---|---|---|
| Layer | Content delivery | Network path | DNS |
| Caches | Yes | No | DNS answers only |
| Traffic | HTTP and HTTPS | TCP and UDP | Name resolution |
| Static IPs | No | Yes, two anycast IPs | Not applicable |
| Reach for it when | Static or cacheable content | Non-HTTP, static IPs, fast regional failover | Routing users by policy |
Route 53 routing policies
| Policy | Use when |
|---|---|
| Simple | One resource |
| Weighted | Split traffic by percentage, such as a canary release |
| Latency | Send users to the fastest Region |
| Failover | Active-passive with health checks |
| Geolocation | Route by the user's location, often for compliance or language |
| Geoproximity | Route by distance, with a bias you can adjust |
| Multivalue answer | Return several healthy records |
CloudFront points to remember
- Keep an S3 origin private with Origin Access Control.
- Use signed URLs or signed cookies for restricted content.
- Attach AWS WAF at the edge for web filtering.
How to tell which the question wants
- Static content, reduce origin load points to CloudFront.
- Static IP addresses, TCP or UDP, gaming or VoIP points to Global Accelerator.
- Route users by country, latency or weight points to Route 53.
A worked scenario: a global website
Requirement: a global site serves images and an API from an ALB, and must keep working if its main Region fails.
- Put CloudFront in front of both S3 and the ALB, and keep the S3 bucket private with Origin Access Control.
- Deploy the application in a second Region.
- Use Route 53 failover routing with health checks so DNS answers point to the healthy Region.
- Attach AWS WAF to CloudFront to filter malicious requests at the edge.
If the same application used UDP or needed fixed IP addresses for firewall allow-lists, Global Accelerator would replace CloudFront in this design.
Details that get tested
- A TLS certificate for CloudFront must be in ACM in us-east-1.
- Alias records point to AWS resources, work at the zone apex and are free for AWS targets.
- Lambda@Edge and CloudFront Functions run logic at the edge.
- S3 Transfer Acceleration speeds up long-distance uploads to S3. CloudFront is mainly for delivery.
How the exam words it
| If the question says | Think |
|---|---|
| Cache static content globally | CloudFront |
| Fixed IPs for allow-lists | Global Accelerator |
| UDP or gaming traffic | Global Accelerator |
| Active-passive between Regions | Route 53 failover |
| Send users to the fastest Region | Route 53 latency |
| Gradual rollout by percentage | Route 53 weighted |
| Point the domain apex at an ALB | Route 53 alias record |
| Speed up uploads to S3 | S3 Transfer Acceleration |
CloudFront vs Global Accelerator: practice questions
Five original questions. Each explanation says why the other options fail.
Your free AWS SAA exam code is ready
Sit the full SAA-C03 paper against the real 130-minute clock. AWS SAA is $39 once, lifetime, future versions included.
AWS-SAA-FULL
Redeem the code
Already have an account? Log in to redeem
Frequently asked questions
What is the difference between CloudFront and Global Accelerator?
CloudFront caches HTTP and HTTPS content at edge locations. Global Accelerator provides static anycast IPs and carries TCP or UDP traffic over the AWS network without caching.
Which Route 53 policy sends users to the fastest Region?
Latency-based routing.
Does Route 53 route actual traffic?
No. Route 53 answers DNS queries. The traffic itself then goes directly to the resource.