Study SOA-C03 DNS, Routing Policies, CloudFront and Global Accelerator: key concepts, common traps, and exam decision cues.
This lesson is about request direction at scale. AWS expects CloudOps engineers to know how Route 53 routing policies, DNS configuration, CloudFront, and Global Accelerator influence where requests go and how content is delivered.
Routing policy: Rule that decides how DNS answers are returned, such as latency-based, weighted, geolocation, or failover logic.
Content delivery: Distribution of content closer to users through caching or optimized network entry points.
Global entry path: The first network path users hit when a service needs fast and resilient worldwide reach into regional endpoints.
AWS wants you to know:
| Requirement | Strongest first fit | Why |
|---|---|---|
| shift traffic gradually between two endpoints | weighted routing | The business need is percentage-based distribution |
| steer users toward the lowest-latency region | latency-based routing | Route 53 should answer with the lowest-latency target |
| use one endpoint unless the primary fails | failover routing | The requirement is primary/secondary continuity |
| answer differently based on user geography | geolocation routing | The business rule is geography-aware DNS response |
| If the stem is mainly about… | Strongest first lane |
|---|---|
| DNS answer logic | Route 53 routing policies |
| edge caching and CDN behavior | CloudFront |
| global anycast-style entry path and health-aware regional steering | Global Accelerator |
| origin-side app distribution inside a region or VPC | ALB or NLB |
flowchart TD
Q["Business requirement"] --> D{"Main need"}
D -->|"DNS answer logic"| R53["Route 53 policy"]
D -->|"Edge caching / CDN"| CF["CloudFront"]
D -->|"Global entry path"| GA["Global Accelerator"]
D -->|"Regional app distribution"| LB["ALB / NLB"]
CF --> ORG["Origin"]
GA --> EP["Regional endpoints"]
The key distinction is that Route 53 answers where the client should go, CloudFront helps serve content from the edge, and Global Accelerator improves the global network entry path into regional application endpoints.
| Trap | Better reading |
|---|---|
| “CloudFront and Global Accelerator are basically the same.” | CloudFront is strongest for caching and CDN behavior, while Global Accelerator is strongest for global application entry-path performance. |
| “If Route 53 is involved, the answer is always a routing policy.” | Sometimes the real issue is not DNS logic but edge caching or endpoint reachability. |
| “Weighted routing and failover mean the same thing.” | Weighted routing distributes traffic intentionally; failover routing preserves a primary/secondary recovery design. |
| “CloudFront is the best answer for any worldwide application requirement.” | If the stem emphasizes global application entry and endpoint health rather than caching, think Global Accelerator first. |
A company runs the same application in multiple AWS regions. The stem says users should enter through a highly available global path and then be directed to healthy regional endpoints, but it does not emphasize content caching. Which lane is strongest first?
Correct answer: B. The stem is about application entry-path performance and health-aware endpoint steering, not CDN caching.