SAA-C03 · Question #513
A company recently migrated its application to a VPC on AWS. An AWS Site-to-Site VPN connection connects the company's on-premises network to the VPC. The application retrieves customer data from anot
The correct answer is B. Create an Amazon Route 53 Resolver outbound endpoint. Configure the outbound endpoint to. When AWS workloads must resolve DNS names from on-premises systems over a hybrid network (like VPN or Direct Connect), the best solution is to use Amazon Route 53 Resolver outbound endpoints. The outbound endpoint enables DNS queries to be forwarded from your VPC to on-premises Y
Question
A company recently migrated its application to a VPC on AWS. An AWS Site-to-Site VPN connection connects the company's on-premises network to the VPC. The application retrieves customer data from another system that resides on premises. The application uses an on- premises DNS server to resolve domain records. After the migration, the application is not able to connect to the customer data because of name resolution errors. Which solution will give the application the ability to resolve the internal domain names?
Options
- ALaunch EC2 instances in the VPC. On the EC2 instances, deploy a custom DNS forwarder that
- BCreate an Amazon Route 53 Resolver outbound endpoint. Configure the outbound endpoint to
- CSet up two AWS Direct Connect connections between the AWS environment and the on-premises
- DCreate an Amazon Route 53 public hosted zone for the on-premises domain. Configure the
How the community answered
(43 responses)- A9% (4)
- B81% (35)
- C2% (1)
- D7% (3)
Explanation
When AWS workloads must resolve DNS names from on-premises systems over a hybrid network (like VPN or Direct Connect), the best solution is to use Amazon Route 53 Resolver outbound endpoints. The outbound endpoint enables DNS queries to be forwarded from your VPC to on-premises You must also configure a Route 53 Resolver forwarding rule to define which domain names (e.g., corp.internal) should be forwarded to the specific on-premises DNS IPs. This setup allows private DNS resolution from AWS to on-premises systems and is fully managed, eliminating the need to run and maintain EC2-based DNS proxies (as in option A). Options C and D are incorrect: C is not DNS-specific and doesn't solve name resolution. D misuses a public hosted zone for a private DNS domain.
Community Discussion
No community discussion yet for this question.