Section 10: Route 53

Question 1

Describe the difference between a CNAME and an alias?

Question 2

True/False: You can use a CNAME or an alias to route traffic to a ROOT DNS domain

Answer 2

False - You can only use an Alias. CNAMEs cannot route traffic to a ROOT DNS domain

Question 3

This feature allows you to define how Route 53 responds to DNS queries

Answer 3

Routing Policy

Question 4

A routing policy that routes traffic to a single resource

Answer 4

Simple Routing Policy

Question 5

A routing policy that allows you to allocate specific percentages of traffic to different resources

Answer 5

Weighted Routing Policy

Question 6

A routing policy that redirects users to the resource that has the fastest connection speed

Answer 6

Latency Based Policy

Question 7

A routing policy where you must assign a specific resource as “primary”; traffic is routed to a secondary resource if primary instance is determined to be unhealthy

Answer 7

Failover Routing Policy

Question 8

A routing policy that uses client location to determine routing

Answer 8

Geolocation Routing Policy

Question 9

A routing policy that relies geographic location of users, locations, as well as a bias value to determine routing

Answer 9

Geoproximity Routing Policy

Question 10

This routing policy requires the usage of Route 53 Traffic Flow

Answer 10

Geoproximity Routing Policy

Question 11

A routing policy that allows clients to connect to a subset of many IPs associated with one DNS hostname

Answer 11

Multi Value Routing Policy

Question 12

You have purchased mycoolcompany.com on Amazon Route 53 Registrar and would like the domain to point to your Elastic Load Balancer my-elb-1234567890.us-west-2.elb.amazonaws.com. Which Route 53 Record type must you use here?

Answer 12

Alias - CNAME cannot refer to a ROOT hostname

Question 13

You have deployed a new Elastic Beanstalk environment and would like to direct 5% of your production traffic to this new environment. This allows you to monitor for CloudWatch metrics and ensuring that there’re no bugs exist with your new environment. Which Route 53 routing policy allows you to do so?

Answer 13

Weighted Routing Policy

Question 14

You have updated a Route 53 Record’s myapp.mydomain.com value to point to a new Elastic Load Balancer, but it looks like users are still redirected to the old ELB. What is a possible cause for this behavior?

Answer 14

TTL (Time to Live) has not expired yet and the old value is still cached

Question 15

You have an application that’s hosted in two different AWS Regions us-west-1 and eu-west-2. You want your users to get the best possible user experience by minimizing the response time from application servers to your users. Which Route 53 Routing Policy should you choose?

Answer 15

Latency Routing Policy

Question 16

You have a legal requirement that people in any country but France should NOT be able to access your website. Which Route 53 Routing Policy helps you in achieving this?

Answer 16

Geolocation Routing Policy

Question 17

You have purchased a domain on GoDaddy and would like to use Route 53 as the DNS Service Provider. What should you do to make this work?

Answer 17

Create a Public Hosted Zone and update the 3rd party Registrar NS records

Question 18

What are the three entities that a Route 53 Healthcheck can monitor?

Answer 18

1. Endpoints
2. Other Health Checks
3. CloudWatch Alarms

Question 19

True/False: You can use a geolocation routing policy to reduce latency

Answer 19

False - This can only be used to restrict the distribution of content based on user location

Question 20

Which three AWS resources can an alias record redirect queries to?

Answer 20

Amazon S3 Buckets
CloudFront distributions
Another record in the same Route 53 hosted zone

Question 21

True/False: A CNAME record can redirect DNS queries to any DNS record

Answer 21

True

Question 22

Route 53 charges for ________ queries to AWS resources, but does not charge for ________ queries

Answer 22

alias; CNAME