Your company is planning to create a private hosted zone in AWS. They need to ensure that on-premises devices that are connected to AWS through VPN, can reach the resources defined in the private hosted zone. How can this be achieved, ensuring the least effort is put into setting this up?

Answer options:

A.Consider using Route53 Inbound Resolver endpoints for resolving DNS requests.
B.Convert the private hosted zone to a public one.
C.Create an EC2 instance and install a DNS resolver.
D.Create an EC2 instance and install AD Domain services.

Answer – A
When you create a VPC using Amazon VPC, Route 53 Resolver automatically uses a Resolver on the VPC to answer DNS queries for local Amazon VPC domain names for EC2 instances (ec2-192-0-2-44.compute-1.amazonaws.com) and records in private hosted zones (acme.example.com).
The Resolver additionally contains endpoints that you configure to answer DNS queries to and from your on-premises environment.
This is also mentioned in the AWS Documentation.
Option B is incorrect because it is specifically mentioned to use a private hosted zone.
Options C and D are incorrect because this would add maintenance overhead.
For more information on Simple AD and DNS, please refer to the below URL:
https://docs.aws.amazon.com/directoryservice/latest/admin-guide/microsoftadbasestep3.html
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html