ANS-C01 Question 309
Select 3You are designing a hybrid DNS solution for a company that has an on-premises data center and a VPC in AWS. The on-premises environment uses a private DNS zone to resolve internal hostnames, while the VPC uses Route 53 for DNS resolution. The company requires that DNS queries originating from the VPC for on-premises resources are resolved by the on-premises DNS servers, and queries originating from on-premises for AWS resources are resolved by Route 53. Which combination of steps should you implement to achieve this requirement?
- A
Create a Route 53 outbound endpoint in the VPC and configure a forwarding rule pointing to the on-premises DNS servers.
- B
Create a Route 53 inbound endpoint in the VPC and configure the on-premises DNS servers to forward queries for AWS resources to this endpoint.
- C
Configure a VPC Peering connection between the VPC and the on-premises network to enable DNS forwarding.
- D
Use AWS Direct Connect or a VPN connection to establish network connectivity between the VPC and the on-premises environment.
- E
Enable Route 53 Resolver rules for public DNS resolution.
Show answer and explanation
Correct answers: A, B, D
Explanation
To enable hybrid DNS resolution, you need to configure a Route 53 outbound endpoint for forwarding DNS queries from the VPC to on-premises DNS servers and a Route 53 inbound endpoint for forwarding DNS queries from on-premises to Route 53 Resolver in the VPC. Additionally, network connectivity such as AWS Direct Connect or a VPN is required to ensure communication between the VPC and the on-premises environment. VPC Peering and public DNS resolution are not relevant to this specific use case.
- A. Correct.
This is correct because an outbound endpoint allows DNS queries from the VPC to be forwarded to the on-premises DNS servers, which is necessary for resolving on-premises hostnames.
- B. Correct.
This is correct because an inbound endpoint allows the on-premises DNS servers to forward queries for AWS resources to Route 53 Resolver in the VPC.
- C. Incorrect.
This is incorrect because VPC Peering does not provide DNS forwarding functionality and is not required for this scenario.
- D. Correct.
This is correct because network connectivity (via AWS Direct Connect or VPN) is necessary to route DNS queries between the VPC and the on-premises network.
- E. Incorrect.
This is incorrect because enabling Route 53 Resolver rules for public DNS is unrelated to private DNS resolution for on-premises and AWS resources.