Google Professional Cloud Network Engineer Question 163
Select 2Google Cloud PlatformYou are designing a DNS peering and forwarding strategy for a multi-VPC architecture in Google Cloud. VPC A hosts an internal DNS server, and VPC B and VPC C need to use this DNS server for resolving both internal and external domains. How should you configure DNS peering and forwarding to meet this requirement?
- A
Configure DNS peering between VPC A and VPC B, and between VPC A and VPC C.
- B
Set up Cloud DNS forwarding zones in VPC B and VPC C to forward DNS queries to the internal DNS server in VPC A.
- C
Enable Private Google Access for VPC A, VPC B, and VPC C to ensure DNS resolution.
- D
Create a Cloud DNS policy in VPC B and VPC C to route all DNS traffic to VPC A.
- E
Configure a Shared VPC and attach VPC B and VPC C to the Shared VPC to centralize DNS resolution.
Show answer and explanation
Correct answers: A, B
Explanation
To enable DNS resolution using the internal DNS server in VPC A, you need to establish DNS peering between VPC A and the other VPCs (B and C). Additionally, DNS forwarding zones in VPC B and VPC C must be set up to direct DNS queries to the internal DNS server in VPC A. These configurations together ensure proper DNS resolution across the VPCs.
- A. Correct.
Configuring DNS peering between VPC A and VPC B, and between VPC A and VPC C allows VPC B and VPC C to reach the internal DNS server in VPC A.
- B. Correct.
Setting up Cloud DNS forwarding zones in VPC B and VPC C ensures that DNS queries are forwarded to the internal DNS server in VPC A.
- C. Incorrect.
Private Google Access is not relevant to DNS forwarding or peering. It allows private IPs in a VPC to access Google APIs and services but does not help with DNS resolution in this scenario.
- D. Incorrect.
DNS policies are not used to forward traffic between VPCs. They are used for specific routing of DNS queries within a VPC or to external systems, but they can't directly implement cross-VPC forwarding for this use case.
- E. Incorrect.
A Shared VPC is not required for DNS peering or forwarding. This approach would centralize networking but is unrelated to the specific DNS requirement.