AWS Certified Advanced Networking - Specialty
Get started today
Ultimate access to all questions.
Comments
Loading comments...
Ultimate access to all questions.
A company has an AWS Site-to-Site VPN connection linking its VPC to an on-premises network, with the default DHCP options set associated with the VPC. An application running on an Amazon Linux 2 EC2 instance within the VPC needs to retrieve an Amazon RDS database secret stored in AWS Secrets Manager via a private VPC endpoint. Additionally, an on-premises application provides an internal RESTful API service accessible via the URL https://api.example.internal, with internal DNS resolution handled by two on-premises Windows DNS servers.
The EC2 instance's application fails to call the on-premises API service when using the service's hostname but succeeds when using the service's IP address. What steps should the network engineer take to resolve this issue and prevent it from impacting other VPC resources?
A
Create a new DHCP options set that specifies the on-premises Windows DNS servers. Associate the new DHCP options set with the existing VPC. Reboot the Amazon Linux 2 EC2 instance.
B
Create an Amazon Route 53 Resolver rule. Associate the rule with the VPC. Configure the rule to forward DNS queries to the on-premises Windows DNS servers if the domain name matches example.internal.
C
Modify the local host file in the Amazon Linux 2 EC2 instance in the VPMap the service domain name (api.example.internal) to the IP address of the internal API service.
D
Modify the local /etc/resolv.conf file in the Amazon Linux 2 EC2 instance in the VPC. Change the IP addresses of the name servers in the file to the IP addresses of the company's on-premises Windows DNS servers.