ANS-C01 Question 26
Select 2A company has a hybrid cloud architecture with resources deployed both on AWS and in an on-premises data center. They need to design a DNS solution that allows their internal users to resolve domain names for resources in AWS and on-premises seamlessly. Additionally, the solution should allow external users to resolve public AWS-hosted services, such as a website running on Amazon EC2. Which combination of solutions meets these requirements?
- A
Use AWS Route 53 Private Hosted Zones for internal DNS resolution and configure a Route 53 Resolver forwarding rule to route on-premises DNS queries to the on-premises DNS server.
- B
Use AWS Route 53 Public Hosted Zones for public DNS resolution and configure Route 53 Resolver endpoints for bidirectional DNS query resolution between AWS and the on-premises data center.
- C
Deploy an Amazon EC2 instance running a custom DNS server to handle all internal and external DNS queries.
- D
Use AWS Route 53 Private Hosted Zones for the on-premises environment and Route 53 Public Hosted Zones for public AWS-hosted services, with no additional configurations.
- E
Configure Route 53 Public Hosted Zones for all domains and rely on public DNS resolution for both AWS and on-premises resources.
Show answer and explanation
Correct answers: A, B
Explanation
The combination of AWS Route 53 Private Hosted Zones for internal AWS DNS resolution, Route 53 Resolver forwarding rules for on-premises DNS queries, and Route 53 Public Hosted Zones for public-facing services ensures a seamless and secure DNS solution for hybrid environments. This approach utilizes AWS-managed services to simplify configuration while meeting public, private, and hybrid DNS requirements effectively.
- A. Correct.
Correct: AWS Route 53 Private Hosted Zones allow for internal DNS resolution for AWS resources, while Route 53 Resolver forwarding rules can route DNS queries to on-premises DNS servers for hybrid environments.
- B. Correct.
Correct: Route 53 Public Hosted Zones handle DNS resolution for public AWS-hosted services. Route 53 Resolver endpoints enable bidirectional DNS query resolution for hybrid architectures, connecting AWS and on-premises environments.
- C. Incorrect.
Incorrect: Deploying a custom DNS server on Amazon EC2 is not recommended due to the complexity of setup, lack of scalability, and redundancy concerns compared to managed services like Route 53.
- D. Incorrect.
Incorrect: Using only AWS Route 53 Private Hosted Zones for the on-premises environment and Public Hosted Zones for public services with no additional configurations does not address the need for seamless hybrid DNS resolution between AWS and on-premises environments.
- E. Incorrect.
Incorrect: Configuring Route 53 Public Hosted Zones for all domains and relying on public DNS for on-premises resources is insecure and does not meet the requirement for internal DNS resolution.