SOA-C02 · Question #633
A company operates compute resources in a VPC and in the company's on-premises data center. The company already has an AWS Direct Connect connection between the VPC and the on-premises data center…
The correct answer is B. Create an Amazon Route 53 Resolver outbound endpoint. Add the IP addresses of an on-. By creating an Amazon Route 53 Resolver outbound endpoint and configuring forwarding rules to send DNS queries to the on-premises DNS servers, EC2 instances in the VPC can dynamically resolve hostnames in the on-premises data center. This solution leverages AWS managed DNS…
Question
A company operates compute resources in a VPC and in the company's on-premises data center. The company already has an AWS Direct Connect connection between the VPC and the on-premises data center. A SysOps administrator needs to ensure that Amazon EC2 instances in the VPC can resolve DNS names for hosts in the on-premises data center. Which solution will meet this requirement with the LEAST amount of ongoing maintenance?
Options
- ACreate an Amazon Route 53 private hosted zone. Populate the zone with the hostnames and IP
- BCreate an Amazon Route 53 Resolver outbound endpoint. Add the IP addresses of an on-
- CSet up a forwarding rule for reverse DNS queries in Amazon Route 53 Resolver. Set the
- DAdd the hostnames and IP addresses for the on-premises hosts to the /etc/hosts file of each EC2
How the community answered
(44 responses)- A2% (1)
- B80% (35)
- C7% (3)
- D11% (5)
Explanation
By creating an Amazon Route 53 Resolver outbound endpoint and configuring forwarding rules to send DNS queries to the on-premises DNS servers, EC2 instances in the VPC can dynamically resolve hostnames in the on-premises data center. This solution leverages AWS managed DNS forwarding and minimizes ongoing maintenance compared to manually maintaining DNS records or host file configurations.
Topics
Community Discussion
No community discussion yet for this question.