63. Route 53 Geolocation Routing Policy

Geolocation routing lets to choose where your traffic will be sent based on the geographic location of your users (i.e the location from which the DNS queries originate). For example, you might want all queries from Europe to be routed to a fleet of EC2 instances that are specifically configured for European customers. These servers may have local language of European customers and all prices are displayed in Euros. In simple terms, it allows to send European customers to European servers and allows to send US customers to US servers. So its basically routes the traffic based on your users location. Notice the difference between Geolocation Routing Policy and Latency Routing Policy.

Questions:
i. One of the biggest football leagues in Europe has granted the distribution rights for live streaming its matches in the US to a silicon valley based streaming services company. As per the terms of distribution, the company must make sure that only users from the US are able to live stream the matches on their platform. Users from other countries in the world must be denied access to these live-streamed matches. Which of the following options would allow the company to enforce these streaming restrictions? (Select two)
Answer: a. Use Route 53 based geolocation routing policy to restrict distribution of content to only the locations in which you have distribution rights.
b. Use georestriction to prevent users in specific geographic locations from accessing content that you are distributing through a CloudFront web distribution.

Question 1:
Your company hosts many infrastructures in the Tokyo region. As a Solutions Architect, you are trying to replicate these infrastructure configurations on the Singapore and Sydney regions to extend your application. Optimal language selection and routing control is required to satisfy users close to the region.
What do you need to do to achieve optimal language selection for your users and ELB routing control?
Options:
A. Set up geo-location routing on Route53
B. Perform load balancing for all regions using NLB
C. Configure low latency routing on Route53
D. Perform load balancing for all regions using ALB
Answer: A
Explanation
Option 1 is the correct answer. With geo-location routing, resources are selected to handle traffic based on the user’s geographic location. As a result, language display and traffic processing will be easy to implement.
When you create a record, you choose a routing policy, which determines how Amazon Route 53 responds to queries:
Simple routing policy – Use for a single resource that performs a given function for your domain, for example, a web server that serves content for the example.com website.
Failover routing policy – Use this when you want to configure active-passive failover.
Geo-location routing policy – Use when you want to route traffic based on the location of your users.
Geo-proximity routing policy – Use when you want to route traffic based on the location of your resources and, optionally, shift traffic from resources in one location to resources in another.
Latency routing policy – Use when you have resources in multiple AWS Regions and you want to route traffic to the region that provides the best latency.
Multi-value answer routing policy – Use when you want Route 53 to respond to DNS queries with up to eight healthy records selected at random.
Weighted routing policy – Use to route traffic to multiple resources in proportions that you choose.

Question 2:
A company hosts an application on Amazon EC2 instances behind Application Load Balancers in several AWS Regions. Distribution rights for the content require that users in different geographies must be served content from specific regions.
Which configuration meets these requirements?
Options:
A. Configure Amazon CloudFront with multiple origins and AWS WAF
B. Create Amazon Route 53 records with a geoproximity routing policy
C. Create Amazon Route 53 records with a geolocation routing policy
D. Configure Application Load Balancers with multi-Region routing
Answer: C
Explanation
To protect the distribution rights of the content and ensure that users are directed to the appropriate AWS Region based on the location of the user, the geolocation routing policy can be used with Amazon Route 53.
Geolocation routing lets you choose the resources that serve your traffic based on the geographic location of your users, meaning the location that DNS queries originate from.
When you use geolocation routing, you can localize your content and present some or all of your website in the language of your users. You can also use geolocation routing to restrict distribution of content to only the locations in which you have distribution rights.
CORRECT: “Create Amazon Route 53 records with a geolocation routing policy” is the correct answer.
INCORRECT: “Create Amazon Route 53 records with a geoproximity routing policy” is incorrect. Use this routing policy when you want to route traffic based on the location of your resources and, optionally, shift traffic from resources in one location to resources in another.
INCORRECT: “Configure Amazon CloudFront with multiple origins and AWS WAF” is incorrect. AWS WAF protects against web exploits but will not assist with directing users to different content (from different origins).
INCORRECT: “Configure Application Load Balancers with multi-Region routing” is incorrect. There is no such thing as multi-Region routing for ALBs.

Question 3:
One of the biggest football leagues in Europe has granted the distribution rights for live streaming its matches in the US to a silicon valley based streaming services company. As per the terms of distribution, the company must make sure that only users from the US are able to live stream the matches on their platform. Users from other countries in the world must be denied access to these live-streamed matches.
Which of the following options would allow the company to enforce these streaming restrictions? (Select two)
A. Use Route 53 based geolocation routing policy to restrict distribution of content to only the locations in which you have distribution rights
B. Use Route 53 based latency routing policy to restrict distribution of content to only the locations in which you have distribution rights
C. Use Route 53 based weighted routing policy to restrict distribution of content to only the locations in which you have distribution rights
D. Use georestriction to prevent users in specific geographic locations from accessing content that you’re distributing through a CloudFront web distribution
E. Use Route 53 based failover routing policy to restrict distribution of content to only the locations in which you have distribution rights
Answer: A & D
Explanation
Correct options:
Use Route 53 based geolocation routing policy to restrict distribution of content to only the locations in which you have distribution rights
Geolocation routing lets you choose the resources that serve your traffic based on the geographic location of your users, meaning the location that DNS queries originate from. For example, you might want all queries from Europe to be routed to an ELB load balancer in the Frankfurt region. You can also use geolocation routing to restrict the distribution of content to only the locations in which you have distribution rights.
Use georestriction to prevent users in specific geographic locations from accessing content that you’re distributing through a CloudFront web distribution
You can use georestriction, also known as geo-blocking, to prevent users in specific geographic locations from accessing content that you’re distributing through a CloudFront web distribution. When a user requests your content, CloudFront typically serves the requested content regardless of where the user is located. If you need to prevent users in specific countries from accessing your content, you can use the CloudFront geo restriction feature to do one of the following: Allow your users to access your content only if they’re in one of the countries on a whitelist of approved countries. Prevent your users from accessing your content if they’re in one of the countries on a blacklist of banned countries. So this option is also correct.
Incorrect options:
Use Route 53 based latency routing policy to restrict distribution of content to only the locations in which you have distribution rights – Use latency based routing when you have resources in multiple AWS Regions and you want to route traffic to the region that provides the lowest latency. To use latency-based routing, you create latency records for your resources in multiple AWS Regions. When Route 53 receives a DNS query for your domain or subdomain (example.com or acme.example.com), it determines which AWS Regions you’ve created latency records for, determines which region gives the user the lowest latency, and then selects a latency record for that region. Route 53 responds with the value from the selected record, such as the IP address for a web server.
Use Route 53 based weighted routing policy to restrict distribution of content to only the locations in which you have distribution rights – Weighted routing lets you associate multiple resources with a single domain name (example.com) or subdomain name (acme.example.com) and choose how much traffic is routed to each resource. This can be useful for a variety of purposes, including load balancing and testing new versions of the software.
Use Route 53 based failover routing policy to restrict distribution of content to only the locations in which you have distribution rights – Failover routing lets you route traffic to a resource when the resource is healthy or to a different resource when the first resource is unhealthy. The primary and secondary records can route traffic to anything from an Amazon S3 bucket that is configured as a website to a complex tree of records
Weighted routing or failover routing or latency routing cannot be used to restrict the distribution of content to only the locations in which you have distribution rights. So all three options above are incorrect.