# Geographic Routing

Geographic routing directs requests to different application endpoints according to the geographic location associated with the requester.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/geographic-routing

> Geographic routing maps locations such as countries, continents, or geographic areas to selected destinations, commonly through DNS responses. It helps engineers deliver localized applications and control regional traffic distribution, but its accuracy depends on how location is inferred and it does not independently enforce data residency.

Practice exams covering Geographic Routing: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Geographic Routing

Effective geographic routing requires explicit location mappings, realistic resolver assumptions, tested health and fallback behavior, and separate controls for residency and access.

1. **Location-to-endpoint mapping**: Associate geographic areas with application destinations and define precedence for overlapping matches. Include a deliberate default for unmatched or unidentifiable locations.
2. **Resolver-dependent location signals**: DNS routing commonly uses the recursive resolver's address or an EDNS Client Subnet prefix. Validate behavior through corporate resolvers, VPNs, and hybrid forwarding paths because these can change the apparent requester location.
3. **Distinct traffic-selection criteria**: Geographic routing selects by location, latency routing selects using latency measurements or estimates, and weighted routing selects according to relative weights. Choose the criterion that matches the requirement rather than treating the policies as interchangeable.
4. **Explicit health and fallback design**: Combine geographic mappings with supported health evaluation and permitted backup destinations. Test all-unhealthy behavior and ensure that fallback does not send traffic to a prohibited region.
5. **DNS caching and resolution boundaries**: TTL values affect how quickly clients can receive changed answers, while private zones and forwarding rules determine which authority is consulted. Neither DNS policy changes nor health changes relocate existing application connections.
6. **Separation from residency enforcement**: Use geographic routing to guide clients toward suitable deployments, not to prove their location or enforce data residency. Apply separate controls to data storage, replication, application processing, and access.

## Cloud services for Geographic Routing

Amazon Route 53 and Azure Traffic Manager apply geographic selection at the DNS layer, allowing a shared application hostname to direct different populations toward selected deployments. In a multi-cloud design, establish a clear authoritative DNS hierarchy and delegate or reference provider-managed names deliberately. Regional endpoints still need application load balancing, health monitoring, and suitable data placement. Hybrid resolvers and private namespaces determine whether clients reach these public policies, so test the complete resolution path alongside geographic mappings, caching, and failure behavior.

- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Implements DNS geolocation routing with continent, country, and United States state mappings, alongside a default location. Its separate latency, weighted, geoproximity, and failover policies address different selection requirements; private zones and Resolver forwarding must be designed so queries reach the intended authority.

## Geographic Routing exam questions

Real practice exam questions on Geographic Routing, with the correct answer and its explanation.

### Question 1 (SAP-C03)

**Question:**

A multinational company operates localized application deployments in Canada, India, and the United States under one public hostname. Amazon Route 53 records assign DNS queries associated with Canada to the Canadian deployment, queries associated with India to the Indian deployment, and all other queries to the US deployment. These assignments must take precedence over network latency.

Branch devices send DNS queries to branch forwarding servers, which forward them to a centrally managed recursive resolver in the United States. The central resolver currently sends authoritative queries without client-subnet information. During a pilot, Canadian and Indian branches consistently receive the US endpoint. Tests using recursive resolvers in each branch's country return the intended endpoint.

Each branch has a stable public IPv4 prefix that is correctly mapped to its country by the DNS geolocation service. The branch forwarders and central resolver support EDNS Client Subnet and subnet-aware caching. The company must retain centralized recursive resolution and must not maintain branch-specific overrides for application hostnames.

Which change will make endpoint selection reflect each branch's public network location while preserving the existing country assignments?

**Correct answer:** Configure branch forwarders to include an EDNS Client Subnet value representing the branch's public network prefix. Configure the central resolver to preserve that information in authoritative queries and cache responses according to their returned subnet scope.

**Explanation:** Route 53 can use EDNS Client Subnet information to make geographic routing decisions instead of relying only on the recursive resolver's location. Supplying the branch's correctly geolocated public prefix preserves the existing country assignments. Subnet-aware caching prevents an answer obtained for one client network from being incorrectly reused for another.

### Question 2 (ANS-C01)

**Question:**

A company hosts api.example.com in a public Route 53 hosted zone managed by a central networking account. The application has a legacy deployment and a replacement deployment behind separate internet-facing Application Load Balancers (ALBs) in eu-west-1. A third ALB serves the application in us-east-1. Each deployment is managed in a different AWS account.

For DNS queries that Route 53 identifies as originating in Europe, the company wants approximately 90% of authoritative DNS selections to return the legacy European deployment and 10% to return the replacement European deployment. All other queries, including queries whose location cannot be determined, must return the US deployment. If either European deployment becomes unhealthy, European queries must receive the other European deployment. Assume that at least one European deployment remains healthy and that the US deployment remains healthy.

Which Route 53 configuration meets these requirements without application changes?

**Correct answer:** Create geolocation alias A records for api.example.com: a Europe record targeting eu-pool.example.com and a default record targeting the US ALB. At eu-pool.example.com, create weighted alias A records targeting the European ALBs with weights of 90 and 10. Enable Evaluate Target Health on the aliases.

**Explanation:** The geolocation records first select the European pool or the default US destination. The weighted records then distribute European DNS selections in a 90:10 ratio. Evaluate Target Health allows the weighted aliases to exclude an unhealthy ALB, so the remaining healthy European deployment receives European selections. An alias can target another record in the same hosted zone, allowing these policies to be composed. ALBs in other accounts can be specified as alias targets using their DNS names and hosted zone IDs.

## Practice Geographic Routing in a full exam

Questions on Geographic Routing in each practice exam, with every answer option and an explanation for each:

- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 2 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 2 questions

## What is Geographic Routing

Geographic routing is a traffic-management technique that selects a destination using the geographic location associated with a request. A common implementation uses authoritative DNS: the same application hostname returns different endpoint addresses for different locations. An organization might direct requests associated with European countries to a European deployment and requests associated with Japan to a Japanese deployment. The policy expresses an intended geographic assignment rather than discovering the fastest destination for every connection.

In DNS-based implementations, the authoritative server usually sees the recursive resolver's address rather than the end user's address. When supported, EDNS Client Subnet can supply a client network prefix that improves location selection. Neither mechanism provides an exact physical location. Corporate resolvers, VPNs, centralized DNS forwarding, and IP geolocation errors can cause users to receive answers associated with a different area. Test from representative client networks and inspect the resolver path instead of assuming that a user's country determines the answer.

Geographic routing differs from latency-based routing and weighted routing. Latency-based routing selects among destinations using the provider's network-latency measurements or estimates; the lowest-latency destination is not necessarily the geographically closest one. Weighted routing distributes DNS answers according to configured relative weights, not geography, and does not guarantee an exact percentage of application requests because resolvers cache answers and clients generate unequal traffic volumes. Geoproximity routing is another distinct mechanism: it uses resource and requester locations, sometimes with configurable bias, to adjust geographic catchment areas rather than simply mapping named countries to endpoints.

Cloud DNS platforms can combine these decisions through supported policy trees or separate DNS names. For example, a geographic decision can select a regional application name, and a second decision can distribute answers between deployments within that region. In Amazon Route 53, geolocation policies support continent, country, and United States state selections, with more-specific matches taking precedence. A default record handles locations without an explicit match or locations that cannot be identified. Without a suitable default or matching record, some queries may receive no usable answer.

Health handling must be designed separately from geographic preference. A location mapping alone does not establish an acceptable backup destination. Associate supported health checks or target-health evaluation with the policy, define permitted fallback destinations, and verify the provider's behavior when every eligible endpoint is unhealthy. Some routing systems can return unhealthy destinations under all-unhealthy conditions. An automatic fallback across a national boundary may improve availability while violating an application's placement requirements.

Hybrid and multi-account DNS introduce additional resolution boundaries. Public authoritative policies, private hosted zones, conditional forwarding rules, and inbound or outbound resolver endpoints perform different jobs. A private zone can shadow a public hostname, preventing the public geographic policy from being consulted. Centralizing queries through an on-premises resolver can also change the location signal observed by public DNS. Sharing forwarding rules across accounts does not, by itself, implement geographic traffic selection.

DNS caching makes policy changes and failover non-instantaneous. Shorter TTLs can reduce answer persistence but increase query volume, and existing connections are not moved by a new DNS response. Validate regional answers, endpoint health, fallback behavior, and application dependencies together. Finally, treat geographic routing as a steering mechanism, not an authorization or compliance boundary: enforce residency through application behavior, storage placement, replication controls, and access policies.

## Learn Geographic Routing in lessons

2 short lessons on Geographic Routing in 1 certification course.

- SAP-C03: Geographic Routing: location-to-Region policies (Premium), https://app.blowstack.com/lessons/geographic-routing-location-to-region-policies-sap-c03
- SAP-C03: Geographic Routing vs Latency-Based Routing (Premium), https://app.blowstack.com/lessons/geographic-routing-vs-latency-based-routing-sap-c03
