Study SOA-C03 DNS, Routing Policies, CloudFront and Global Accelerator: key concepts, common traps, and exam decision cues.
This lesson covers SOA-C03 Task 5.2: configuring domains, DNS services, and content delivery. AWS is testing whether you can separate DNS decision logic from CDN behavior and from global application entry performance. Strong answers identify whether the real requirement is about name resolution, routing policy, edge caching, or global endpoint acceleration.
Routing policy: Rule that decides how Route 53 answers client queries, such as weighted, failover, latency-based, or geolocation behavior.
Resolver: DNS service path used to resolve names inside AWS and hybrid environments.
Global entry path: First network entry into an application when global users need to reach healthy regional endpoints quickly.
AWS wants you to know:
| Requirement | Strongest first fit | Why |
|---|---|---|
| send a percentage of traffic to one endpoint and the rest elsewhere | weighted routing | The business requirement is controlled distribution. |
| direct users to the lowest-latency region | latency-based routing | The answer is about DNS steering by latency. |
| use a primary endpoint unless it becomes unhealthy | failover routing | The business requirement is primary/secondary continuity. |
| answer differently based on user geography | geolocation routing | The business rule is geography-aware DNS behavior. |
| If the stem is mainly about… | Strongest first lane |
|---|---|
| internal or hybrid DNS resolution behavior | Route 53 Resolver |
| hosted zones, records, query logging, and DNS answer policy | Route 53 DNS configuration |
| edge caching and CDN behavior | CloudFront |
| global anycast-style application entry path and regional endpoint health steering | Global Accelerator |
This is one of the highest-yield SOA-C03 distinctions.
| If the question is mainly about… | Think first about… |
|---|---|
| caching content close to users | CloudFront |
| reducing origin load through cached delivery | CloudFront |
| globally accelerating entry into healthy application endpoints | Global Accelerator |
| application traffic where the key requirement is not caching but resilient global entry | Global Accelerator |
If the stem emphasizes content caching, edge behavior, or origin selection, CloudFront is usually stronger. If it emphasizes global application entry, healthy regional endpoints, or accelerated user path without making caching the point, Global Accelerator is usually stronger.
When these services appear together, work in layers:
This layered thinking is stronger than assuming every global problem is a CloudFront issue.
| Trap | Better thinking |
|---|---|
| “CloudFront and Global Accelerator are basically the same.” | CloudFront is strongest for CDN and edge caching; Global Accelerator is strongest for global application entry-path performance. |
| “If Route 53 appears, the answer must be a routing policy.” | Sometimes the real issue is Resolver behavior, query logging, or CDN versus endpoint path choice. |
| “Weighted and failover routing are close enough.” | Weighted deliberately distributes traffic; failover preserves a primary/secondary behavior. |
| “CloudFront is the best global answer by default.” | If caching is not the point and endpoint health steering is, think Global Accelerator. |
A company runs the same application in multiple Regions. Users must enter through a highly available global path and be directed to healthy regional endpoints. The requirement does not emphasize content caching.
Which lane is strongest first?
Correct answer: 2
Why: The requirement is about resilient global application entry and health-aware endpoint steering, not CDN caching.