A company runs an application in a VPC on AWS. The company's on-premises data center has a DNS server. The data center is connected to AWS through an AWS Direct Connect connection with a private…

Question

Options

• ASet up AWS Verified Access endpoints in the VPC. Configure DNS forwarding rules in Verified
• BConfigure the Direct Connect connection to enable DNS resolution between the on-premises
• CCreate an Amazon Route 53 Resolver outbound endpoint and a Resolver rule in the VPC.
• DCreate an Amazon Route 53 Resolver inbound endpoint in the VPC. Configure the on-premises

• A
  16% (8)
• B
  10% (5)
• C
  4% (2)
• D
  71% (36)

Explanation

When on-premises DNS servers need to resolve private DNS names in a VPC, the correct pattern is to create a Route 53 Resolver inbound endpoint. The inbound endpoint allows DNS queries to flow from the on-premises environment into the VPC, where Route 53 can resolve VPC-specific names (such as private hosted zones or private resource records). Outbound endpoints (C) are for sending VPC DNS queries to on-premises, not the reverse. Verified Access (A) is unrelated to DNS resolution. Direct Connect (B) provides network connectivity but does not provide DNS forwarding capabilities. Therefore, option D is the correct design.

No community discussion yet for this question.