ANS-C01 Question 292
Select 2Your company has a hybrid cloud setup with resources in both an on-premises data center and AWS. The on-premises environment uses a private DNS zone for internal workloads, while workloads in AWS are configured to use Amazon Route 53 as their DNS service. You need to ensure that AWS-based resources can resolve on-premises domain names and on-premises resources can resolve AWS domain names. Which approach should you take?
- A
Configure an Amazon Route 53 Resolver outbound endpoint in your VPC and set up forwarding rules for the on-premises DNS zone.
- B
Use AWS Direct Connect and configure the on-premises DNS server to forward queries for AWS zones to Route 53 Resolver inbound endpoints.
- C
Enable DNS resolution in the VPC and associate it with the on-premises DNS server using a Transit Gateway.
- D
Deploy an EC2 instance in the VPC to run a custom DNS forwarder and configure it to forward queries between the on-premises DNS and Route 53.
- E
Configure Route 53 Resolver inbound and outbound endpoints in the VPC, and set up bidirectional forwarding rules for both AWS and on-premises zones.
Show answer and explanation
Correct answers: A, E
Explanation
To enable bidirectional DNS resolution between AWS and an on-premises environment in a hybrid setup, you need to configure Route 53 Resolver endpoints. An outbound endpoint is required to forward DNS queries from AWS to the on-premises DNS server, and an inbound endpoint is required for the on-premises DNS server to forward queries to Route 53 Resolver. This approach ensures seamless name resolution across both environments without the need for custom solutions.
- A. Correct.
This is correct because an outbound endpoint allows Route 53 Resolver to forward DNS queries to the on-premises DNS server for domains it cannot resolve locally.
- B. Incorrect.
This is a valid option because forwarding queries to a Route 53 Resolver inbound endpoint enables on-premises resources to resolve AWS domain names.
- C. Incorrect.
This is incorrect because enabling DNS resolution in a VPC does not provide functionality for cross-environment DNS resolution. Transit Gateway does not natively support DNS forwarding.
- D. Incorrect.
This is incorrect because deploying a custom DNS forwarder on an EC2 instance is not necessary when Route 53 Resolver provides a managed solution for DNS forwarding.
- E. Correct.
This is correct because configuring both inbound and outbound Route 53 Resolver endpoints allows for bidirectional DNS resolution between the AWS environment and the on-premises environment.