AWS Certified Advanced Networking - Specialty ANS-C01Demo

By Amazon · Question Mode

QuestionQ191

Network Design

A network engineer is designing private DNS integration between AWS workloads and on-premises resources. The AWS deployment includes five VPCs in the eu-west-1 Region, connected to the on-premises network through AWS Direct Connect. The VPCs communicate with one another using a transit gateway. Each VPC is associated with a private hosted zone that uses the aws.example.internal domain. The network engineer creates an Amazon Route 53 Resolver outbound endpoint in a shared services VPC and attaches that VPC to the transit gateway.

The network engineer is implementing DNS resolution. Queries for hostnames ending in aws.example.internal must use the private hosted zone. Queries for hostnames ending in every other domain must be forwarded to a private on-premises DNS resolver.

Which solution meets these requirements?

  • A Add a forwarding rule for “*” that targets the on-premises server's DNS IP address. Add a system rule for aws.example.internal that targets Route 53 Resolver.
  • B Add a forwarding rule for aws.example.internal that targets Route 53 Resolver. Add a system rule for “.” that targets the Route 53 Resolver outbound endpoint.
  • C Add a forwarding rule for “*” that targets the Route 53 Resolver outbound endpoint.
  • D Add a forwarding rule for “.” that targets the Route 53 Resolver outbound endpoint.
Explanation

A Route 53 Resolver forwarding rule for . acts as the catch-all rule and forwards unmatched DNS queries through the specified outbound endpoint to the on-premises resolver. Resolver automatically creates rules for associated private hosted zones, so queries for records in aws.example.internal continue to resolve from that private hosted zone despite the less-specific . forwarding rule. AWS: How VPC Resolver determines where to forward DNS queries

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!