AWS ROUTE 53 - OVERVIEW EXAM QUESTIONS

PDF Download

AWS ROUTE 53 - OVERVIEW EXAM QUESTIONS

Actual Qs and Ans Expert-Verified Explanation

This Exam contains:

-Guarantee passing score -63 Questions and Answers -format set of multiple-choice -Expert-Verified Explanation

Question 1: How does Amazon Route 53 provide high availability and low latency?

Answer:

Route 53 is built using AWS's highly available and reliable infrastructure. The globally distributed nature of our DNS servers helps ensure a consistent ability to route your end users to your application by circumventing any internet or network related issues.Route 53 is designed to provide the level of dependability required by important applications. Using a global anycast network of DNS servers around the world, Route 53 is designed to automatically answer queries from the optimal location depending on network conditions. As a result, the service offers low query latency for your end users.

Question 2: What is a SOA record?

Answer:

Start of Authority Record. Every zone has one and only one SOA resource record.

• Who is the owner
• The authoritative server
• serial number
• The refreshing time/cycle and the TTL

Question 3: Can I create multiple hosted zones for the same domain name?

Answer:

Yes . Creating multiple hosted zones allows you to verify your DNS setting in a "test" environment, and then replicate those settings on a "production" hosted zone. For example, hosted zone Z1234 might be your test version of example.com, hosted on name servers ns-1, ns-2, ns-3, and ns-4. Similarly, hosted zone Z5678 might be your production version of example.com, hosted on ns-5, ns-6, ns-7, and ns-8. Since each hosted zone has a virtual set of name servers associated with that zone, Route 53 will answer DNS queries for example.com differently depending on which name server you send the DNS query to.

Question 4: What does Route 53 create for each public hosted zone?

Answer:

• records are created

:

1) Name Server (NS) record

• This lists the
• name servers that are the authoritative name servers for you hosted zone

.

2) Start of Authority (SOA) These should not be changed!

Question 5: Can you maintain an internal and external version of the same site?

Answer:

Yes, You can use Route 53 to configure split-view DNS , also known as split-horizon DNS. If you want to maintain internal and external versions of the same website or application (for example, for testing changes before you make them public), you can configure public and private hosted zones to return different internal and external IP addresses for the same domain name .Just create a public hosted zone and a private hosted zone that have the same domain name, and create the same subdomains in both hosted zones.

Question 6: What are the different types of hosted zones?

Answer:

There are two types of hosted zones:

?Public hosted zones contain records that specify how you want to route traffic on the internet . For more information, see Working with Public Hosted Zones (p. 221).?Private hosted zones contain records that specify how you want to route traffic in an Amazon VPC . For more information, see Working with Private Hosted Zones (p. 233).Question 7: Can I point my zone apex (example.com versus www.example.com) at my Amazon CloudFront distribution?

Answer:

Yes .Amazon Route 53 offers a special type of record called an 'Alias' record that lets you map your zone apex (example.com) DNS name to your Amazon CloudFront distribution (for example, d123.cloudfront.net) .IP addresses associated with Amazon CloudFront endpoints vary based on your end user's location (in order to direct the end user to the nearest CloudFront edge location) and can change at any time due to scaling up, scaling down, or software updates. Route 53 responds to each request for an Alias record with the IP address(es) for the distribution.Question 8: What are the steps for creating white label name servers for reuse with multiple names?

Answer:

Step 1: Create a Route 53 reusable delegation set

Step 2: Create or recreate Amazon Route 53 hosted zones, and change the TTL for NS and SOA records

Step 3: Recreate records for your hosted zones

Step 4: Get IP addresses

Step 5: Create records for white label name servers

Step 6: Update NS and SOA records

Step 7: Create glue records and change the registrar's name servers

Step 8: Monitor traffic for the website or application

Step 9: Change TTLs back to their original values

Step 10: (Optional) Contact recursive DNS services

Question 9: Can you set the TTL for Alias record types?

Answer:

No for certain resource types. This includes:

• CloudFront
• Elastic Beanstalk
• ELB
• S3

If the alias record points to another record in the same zone, it will use that records TTL.

Question 10: What can I do with Amazon Route 53?

Answer:

- create and manage your public DNS records

• Route 53 also

answers requests to translate specific domain names into their corresponding IP addresses

• use Route 53 to

create DNS records for a new domain or transfer DNS records for an existing domain - REST API for Route 53 allows you to easily create, update and manage DNS records

• provides

health checks to monitor the health and performance of your application as well as your web servers and other resources - register new domain names or transfer in existing domain names to be managed by Route 53 Question 11: Why does the DNS Query Test Tool return a response different than the dig or nslookup commands?

Answer:

When resource record sets are changed in Amazon Route 53, the service propagates updates you make to your DNS records to its world-wide network of authoritative DNS servers .If you test the record before propagation is complete, you may see an old value when you use the dig or nslookup utilities .Additionally, DNS resolvers on the internet are outside the control of the Amazon Route 53 service and will cache your resource record sets according to their time to live (TTL), which means a dig/nslookup command might return a cached value .