A food production company is having hybrid connectivity between regional Data Centre & AWS VGW using AWS Direct Connect link. VPC A & VPC B is created to deploy multiple servers accessed by users in regional offices. A private hosted zone is created for a new domain hosted on one of the servers in VPC
B. Route 53 Resolver inbound endpoint is created in VPC A for a large volume of DNS queries from users in regional offices. These users are complaining of DNS queries failing for domains created in a private hosted zone but working for other domains hosted in VPC.Which of the following actions need to be taken to resolve the issue?

Answer options:

A.The existing Inbound endpoint is loaded, implementing another inbound endpoint in VPC A to cater traffic from on-premises users to private hosted zones.
B.VPC peering needs to be enabled between VPC A & VPC
B.C.Private Hosted Zone needs to be created in VPC A, where an inbound endpoint is created.
D.enableDnsHostnames & enableDnsSupport need to be enabled in VPC A.

Correct Answer – C
It should be in the same VPC where Route 53 Resolver inbound endpoint is created for Private Hosted zones. In the above case, Route 53 Resolver inbound endpoint is created in VPC A. So, a private hosted zone needs to be created in this VPC A.Option A is incorrect as Creating another endpoint in VPC A will not resolve issues faced by users for private hosted zones in VPC
B. Also, for loaded endpoints, the best practice is to add an additional IP address to the endpoint instead of creating a new endpoint.
Option B is incorrect as VPC peering is not required to be enabled for sharing inbound endpoints between VPCs.
Option D is incorrect as these attributes need to be set for the VPC to enable DNS resolution on instances launched within VPC. These attributes will be required at VPC, but this will not cause query failures for on-premises users to sub-domain names.
For more information on AWS Route 53 Resolver inbound endpoints, refer to the following URL
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html#resolver-considerations-inbound-endpoint-private-zone