A company has an on-premises DNS solution and wants to resolve DNS records in an Amazon Route 53 private hosted zone for example.com. The company has set up an AWS Direct Connect connection for…

Question

Options

• ACreate a Route 53 Resolver inbound endpoint. Attach a security group to the endpoint to allow
• BCreate a Route 53 Resolver inbound endpoint. Attach a security group to the endpoint to allow
• CCreate a Route 53 Resolver outbound endpoint. Attach a security group to the endpoint to allow
• DCreate a Route 53 Resolver outbound endpoint. Attach a security group to the endpoint to allow

• A
  76% (22)
• B
  7% (2)
• C
  14% (4)
• D
  3% (1)

Explanation

According to AWS Cloud Operations and Networking documentation, Route 53 Resolver inbound endpoints allow DNS queries to originate from on-premises DNS servers and resolve private hosted zone records in AWS. The inbound endpoint provides DNS resolver IP addresses within the VPC, which the on-premises DNS servers can forward queries to over AWS Direct Connect or VPN connections. The inbound endpoint must be associated with a security group that permits inbound traffic on TCP and UDP port 53 from the on-premises DNS server IP addresses. This ensures that DNS requests from the on-premises environment reach the VPC Resolver for resolution of private domains like example.com. By contrast, outbound endpoints are used for the opposite direction--resolving external (on- premises or internet) DNS names from within AWS VPCs. Therefore, only an inbound endpoint correctly satisfies the direction of resolution in this scenario.

No community discussion yet for this question.