Type of Record Set Not Supported in Private Hosted Zone | AWS Certified Advanced Networking - Specialty Exam | Amazon

Type of Record Set Not Supported in Private Hosted Zone

Prev Question Next Question

Question

Which of the following is a type of record set that cannot be created for a private hosted zone in Route53.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Answer - A.

You can use the following routing policies when you create resource record sets in a private hosted zone:

Simple.

Failover.

Weighted.

Note: Private hosted zone does not have internet connection and hence "geolocation" record set of Route53 cannot be used with private hosted zone.

For more information on Private hosted zones, please visit the below link:

http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-private.html

The correct answer is A. Geolocation.

Amazon Route 53 is a highly available and scalable cloud Domain Name System (DNS) web service. It is used to route internet traffic to resources such as EC2 instances, S3 buckets, and load balancers. Amazon Route 53 also enables you to create and manage public and private DNS namespaces.

A hosted zone is a container for DNS records, and it contains information about how you want to route traffic for a specific domain and its subdomains. A private hosted zone is a DNS namespace that you can create in your VPC. It enables you to resolve DNS queries for resources in your VPC without exposing DNS data to the public internet.

Route 53 supports different types of record sets, such as A, AAAA, CNAME, MX, NS, PTR, SOA, SPF, SRV, and TXT. These record sets serve different purposes, such as mapping domain names to IP addresses, defining email servers, and providing information about domain ownership and authentication.

However, not all record set types can be created for a private hosted zone in Route 53. The question asks which type of record set cannot be created for a private hosted zone, and the answer is A. Geolocation.

Geolocation record sets are used to route traffic based on the geographic location of the end user. They allow you to create different routing policies for different regions or countries. However, geolocation record sets require that the DNS queries come from the public internet, and they cannot be used in a private hosted zone.

The other record set types listed in the question can be created for a private hosted zone in Route 53. Here is a brief explanation of each:

B. Simple record sets are used to map a domain name to one or more IP addresses or Elastic Load Balancers (ELBs).

C. Failover record sets are used to create a primary and secondary resource for failover scenarios. The primary resource handles traffic as long as it is healthy, and the secondary resource takes over if the primary resource becomes unhealthy.

D. Weighted record sets are used to distribute traffic across multiple resources based on a weighting value that you assign. For example, you can send 80% of traffic to one resource and 20% to another resource.

In summary, when creating record sets in a private hosted zone in Route 53, you cannot create geolocation record sets.