For a project with many VPCs, VPC peering has been enabled. Your requirement is that a VPC should resolve public IPv4 DNS hostnames to private IPv4 addresses when queried from instances in the peer VPC. What would you do?

Answer options:

A.Enable DNS hostname resolution for your VPC peering connection.
B.Add DNS name resolution in Route53 for private IP address.
C.No changes are required. By default, every instance from each VPC peering addresses each other instance using the DNS hostname resolution to point to the Private IP address. The application team needs to make changes to the application.
D.Disable existing VPC peers & create new VPC peers with enabling DNS resolution with Private IP address & not with Public IP address.

Correct Answer – A
DNS hostname resolution should be enabled for the VPC peering connection.
Option B is incorrect as adding the name resolution in Route53 is not required for VPC peering to resolve to the private IP address.
Option C is incorrect as the DNS hostname resolution should be enabled.
Option D is incorrect as creating a new VPC peering is not required. You can make changes to the existing VPC peering itself.
For more information on DNS resolution with VPC peering, refer to the following URL
https://docs.aws.amazon.com/vpc/latest/peering/modify-peering-connections.html#vpc-peering-dns