AWS Certified Advanced Networking Specialty Practice Exam

Disable ads (and more) with a membership for a one time $4.99 payment

Prepare for the AWS Certified Advanced Networking Specialty Exam with detailed flashcards and multiple-choice questions. Each question includes hints and explanations. Ace your exam with confidence!

Practice this question and more.


In a split-view DNS scenario, which solution makes sure that internal and external access both use the same domain name while utilizing Amazon Route 53?

  1. Create two separate public hosted zones

  2. Create one hosted zone for all VPCs

  3. Create Amazon Route 53 private and public hosted zones for example.com

  4. Use a NAT gateway for access

The correct answer is: Create Amazon Route 53 private and public hosted zones for example.com

In a split-view DNS scenario, the goal is to provide different DNS responses based on the source of the DNS query, typically distinguishing between internal requests (from within a private network) and external requests (from the public internet). By using Amazon Route 53, creating both a public hosted zone and a private hosted zone for the same domain (e.g., example.com) allows for this differentiation while keeping the same domain name consistent for both internal and external users. When you configure a public hosted zone, it serves DNS queries from the internet, directing users to public resources like web servers, while the private hosted zone is specifically for internal queries, serving resources that aren't exposed to the internet, such as internal applications or databases located within a Virtual Private Cloud (VPC). This setup ensures that internal users can access resources associated with the same domain name without needing an alternative name, while external users receive the appropriate DNS records for public-facing resources. This approach is scalable and integrates well with Amazon's resources, as there is no need to manage two different domain names or complicate the DNS infrastructure. Hence, using both a Route 53 private hosted zone and a public hosted zone effectively achieves the goal of maintaining the same domain name for both internal and external access in