Exam AWS Certified Advanced Networking - Specialty ANS-C01 topic 1 question 76 discussion

Single PHZ can be associated with VPCs across regions. D is correct.

This blog is for multi-account DNS architecture, not region. Single PHZ can be associated with multiple VPCs across regions. Option D) is correct

D is right! Route 53 private hosted zones do not support zone transfers

D is the correct answer.

I think that it's correct answer is A according to SPOTO products.

Option D is the most appropriate because it involves creating a single private hosted zone for aws.example.com and associating it with every VPC that has resources. This ensures a centralized management approach. With this approach, you can create DNS records for all resources within the private hosted zone, allowing for a consistent DNS suffix across VPCs and regions. Options A, B, and C do not provide a centralized solution or are not suitable for achieving the desired outcome in a multi-VPC, multi-region environment.

D is the correct answer.

Here are the reasons why Option D is the correct answer: It creates a single private hosted zone for aws.example.com. This ensures that all resources in all VPCs can be accessed using the same domain name. It associates the private hosted zone with every VPC that has resources. This ensures that the DNS records for all resources are replicated to all VPCs. It creates DNS records for all resources in the private hosted zone. This ensures that all resources can be resolved by DNS. Option A is not a valid solution because it would create separate private hosted zones for each Region. This would make it difficult to manage DNS records and would not ensure that all resources are resolved under the same domain name. Option B is not a valid solution because it does not apply the aws.example.com DNS suffix to all resources. Option C is not a valid solution because it does not explicitly associate resources in different VPCs across multiple Regions with the aws.example.com domain name.

Yes D is Correct ,Route 53 is a global resource.

Option D) is correct

https://aws.amazon.com/blogs/architecture/using-route-53-private-hosted-zones-for-cross-account-multi-region-architectures/

Looks like D, no need to create resources DNS name in all regions/VPCs