Explanation:
Route 53 Resolver outbound endpoints allow VPC resources to forward DNS queries for on-premises domains to on-premises DNS servers. This is a scalable, managed solution with low maintenance. Option A requires manual synchronization of hostnames, which is high maintenance. Option D is extremely high maintenance as it requires updating every EC2 instance whenever on-premises hosts change.
Ultimate access to all questions.
Question #24 \nA 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 CloudOps engineer needs to ensure that Amazon EC2 instances in the VPC can resolve DNS names for hosts in the on-premises data center. \nWhich solution will meet this requirement with the LEAST amount of ongoing maintenance?
A
Create an Amazon Route 53 private hosted zone. Populate the zone with the hostnames and IP addresses of the hosts in the on-premises data center.
B
Create an Amazon Route 53 Resolver outbound endpoint. Add the IP addresses of an on-premises DNS server for the domain names that need to be forwarded.
C
Set up a forwarding rule for reverse DNS queries in Amazon Route 53 Resolver. Set the enableDnsHostnames attribute to true for the VPC.
D
Add the hostnames and IP addresses for the on-premises hosts to the /etc/hosts file of each EC2 instance.
E
None
F
None
No comments yet.