QuestionQ1

Network Design

An insurance company plans to migrate workloads from its on-premises data center to the AWS Cloud. The company needs end-to-end domain name resolution, including bi-directional DNS resolution between AWS and the existing on-premises environments. The workloads will be migrated into multiple VPCs, have dependencies on one another, and will not all migrate at the same time.

Which solution fulfills these requirements?

  • A Configure a private hosted zone for each application VPC, and create the requisite records. Create a set of Amazon Route 53 Resolver inbound and outbound endpoints in an egress VPC. Define Route 53 Resolver rules to forward requests for the on-premises domains to the on-premises DNS resolver. Associate the application VPC private hosted zones with the egress VPC, and share the Route 53 Resolver rules with the application accounts by using AWS Resource Access Manager. Configure the on-premises DNS servers to forward the cloud domains to the Route 53 inbound endpoints.
  • B Configure a public hosted zone for each application VPC, and create the requisite records. Create a set of Amazon Route 53 Resolver inbound and outbound endpoints in an egress VPC. Define Route 53 Resolver rules to forward requests for the on-premises domains to the on-premises DNS resolver. Associate the application VPC private hosted zones with the egress VPC. and share the Route 53 Resolver rules with the application accounts by using AWS Resource Access Manager. Configure the on-premises DNS servers to forward the cloud domains to the Route 53 inbound endpoints.
  • C Configure a private hosted zone for each application VPC, and create the requisite records. Create a set of Amazon Route 53 Resolver inbound and outbound endpoints in an egress VPDefine Route 53 Resolver rules to forward requests for the on-premises domains to the on-premises DNS resolver. Associate the application VPC private hosted zones with the egress VPand share the Route 53 Resolver rules with the application accounts by using AWS Resource Access Manager. Configure the on-premises DNS servers to forward the cloud domains to the Route 53 outbound endpoints.
  • D Configure a private hosted zone for each application VPC, and create the requisite records. Create a set of Amazon Route 53 Resolver inbound and outbound endpoints in an egress VPC. Define Route 53 Resolver rules to forward requests for the on-premises domains to the on-premises DNS resolver. Associate the Route 53 outbound rules with the application VPCs, and share the private hosted zones with the application accounts by using AWS Resource Access Manager. Configure the on-premises DNS servers to forward the cloud domains to the Route 53 inbound endpoints.
Explanation

Route 53 Resolver inbound endpoints allow on-premises DNS resolvers to forward AWS private-domain queries into AWS, while outbound endpoints and Resolver forwarding rules allow VPC workloads to resolve on-premises domains. A private hosted zone must be associated with the VPC that hosts the inbound endpoint for that endpoint to resolve records in the zone. Sharing Resolver rules through AWS Resource Access Manager lets the application VPCs use the centralized outbound DNS-forwarding configuration.

Learn more

Community Discussion

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