Google Professional Cloud Network Engineer Question 533
Select 2Google Cloud PlatformYour company is migrating a legacy on-premises application to Google Cloud and needs to set up a private DNS zone for internal resolution of application domains. The application will run in multiple VPCs across different regions. How can you ensure that all VPCs can resolve the private DNS zone?
- A
Create a private DNS zone and associate it with all the required VPCs using DNS peering.
- B
Create a private DNS zone and configure DNS forwarding policies to forward queries to the zone.
- C
Create a private DNS zone and associate it with a Shared VPC, then add all other VPCs as service projects.
- D
Create a private DNS zone and configure inbound and outbound server policies to share DNS resolution across VPCs.
- E
Create a private DNS zone and enable VPC peering between the VPCs where resolution is needed.
Show answer and explanation
Correct answers: A, C
Explanation
To enable DNS resolution for private DNS zones across multiple VPCs, you can either use DNS peering to associate the zone with the required VPCs or utilize a Shared VPC setup where the private DNS zone resides in the host project. Both methods ensure that the DNS records are resolvable across the necessary VPCs, but methods like DNS forwarding policies, server policies, or VPC peering alone do not achieve this.
- A. Correct.
Correct: Associating the private DNS zone with all the required VPCs using DNS peering ensures that the DNS zone is resolvable across multiple VPCs.
- B. Incorrect.
Incorrect: DNS forwarding policies are used for forwarding queries to external DNS servers, not for private DNS zones within Google Cloud.
- C. Correct.
Correct: A Shared VPC can be used to centralize private DNS zones, and service projects can resolve records if they are added to the Shared VPC.
- D. Incorrect.
Incorrect: Inbound and outbound server policies are not applicable for sharing private DNS zones across VPCs. These are used for managing DNS traffic with external systems.
- E. Incorrect.
Incorrect: VPC peering does not automatically share private DNS zones; DNS peering or a Shared VPC is required specifically for DNS resolution.