Subdomain 1.2: Design DNS solutions that meet public, private, and hybrid requirements.
1.A company is provisioning dozens of new VPCs across many AWS accounts each month. Every VPC needs the same set of private hosted zone associations, Resolver forwarding rules, and DNS Firewall rule groups applied consistently, and updates to that configuration should propagate to all VPCs automatically. What is the most operationally efficient way to manage this in Route 53?
- A.A Route 53 Profile with the shared zones, rules, and rule groups, associated to each new VPC
- B.A script that re-associates every hosted zone, Resolver rule, and rule group with each new VPC
- C.AWS RAM sharing the private hosted zones directly with every account that creates a VPC
- D.A CloudFormation template that must be manually redeployed each time a new VPC is provisioned
Show answer & explanation
Correct answer: A — A Route 53 Profile with the shared zones, rules, and rule groups, associated to each new VPC
- A. Route 53 Profiles bundle private hosted zones, Resolver rules, and DNS Firewall rule groups so they can be associated with many VPCs at once, and updates to the Profile propagate automatically to every associated VPC.
- B. A custom script re-associating each resource individually recreates the manual work Profiles are designed to remove, and it doesn't propagate later configuration updates automatically.
- C. AWS RAM doesn't share private hosted zones directly the way it shares Resolver rules or subnets; cross-account hosted zone access instead uses VPC association authorization or Profiles.
- D. Manually redeploying a CloudFormation stack per VPC doesn't scale to dozens of new VPCs a month and requires repeated manual action rather than automatic propagation.