Q1Network 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?
← → navigate · a answer
Community votes
Discussion · 14
10
It is A). PHZ cannot be shared, Route 53 resolver rules can be shared uusing AWS RAM.
A 4
A is correct.
3
D is the correct answer
3
"Associate the Route 53 outbound rules with the application VPCs" -> wrong.
A 3
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.
A 2
A.
B: No. Public zones are for internet-facing domains, not internal VPC resolution. VPCs need private zones for internal DNS.
C: No. Forwarding to outbound endpoints is incorrect. Outbound endpoints send queries from AWS, not receive them. Inbound endpoints are needed.
D: No. Resolver rules need VPC association, but “associate outbound rules with VPCs” is unclear—rules are typically associated via outbound endpoints in the egress VPC. Associating rules directly with application VPCs contradicts the egress VPC model (rules should stay centralized).
A 2
Associate private hosted zoneS with egress VPC, and share forwarding rules (to on-prem DNS) with application VPC's via RAM.
Pay attention to the details and wording.
A is the correct answer.
1
efffff
1
A is right
* associate the private hosted zones with the egress VPC, allowing centralized DNS management, while sharing the rules through RAM for consistency
A 1
A is the right answer.
1
A and C are the same answer. C has some typo's
1
agreed A -
D 1
A is wrong: Resolver rules forward queries to DNS servers. They cannot forward queries to a Route 53 Private Hosted Zone in another VPC.
Private Hosted Zones: provide authoritative DNS for AWS resources and are made available to the VPCs that need them.
1
The use of 'egress zone' bothers me as it *could* indicate Internet which means public zone (B) instead of private zone (A).