Google Professional Cloud Network Engineer Question 560
Select 2Google Cloud PlatformYou are tasked with enabling DNS resolution between two separate VPC networks, VPC-A and VPC-B, in Google Cloud. VPC-A hosts a private Cloud DNS zone, and VPC-B needs to resolve the domain names configured in that zone. Both VPCs are in the same project. What steps do you need to take to achieve DNS peering between the two VPC networks?
- A
Create a DNS peering zone in VPC-B and specify VPC-A as the target network.
- B
Enable VPC peering between VPC-A and VPC-B before setting up DNS peering.
- C
Configure a DNS peering zone in VPC-A and specify VPC-B as the target network.
- D
Ensure the private Cloud DNS zone in VPC-A is shared with VPC-B.
- E
Create a forwarding zone in VPC-B pointing to VPC-A's internal IP addresses.
Show answer and explanation
Correct answers: A, C
Explanation
To enable DNS peering between two VPC networks, you need to configure DNS peering zones in both VPCs, one zone in VPC-A to allow VPC-B to resolve the private zone, and the reciprocal configuration in VPC-B. VPC peering is not required for DNS peering, and forwarding zones are not used in this setup. DNS peering zones are the recommended approach for cross-VPC DNS resolution in Google Cloud.
- A. Correct.
Correct. A DNS peering zone allows VPC-B to resolve domain names hosted in VPC-A's private Cloud DNS zone. This is a key step for DNS peering.
- B. Incorrect.
Incorrect. VPC peering is not required for DNS peering. DNS peering can be set up independently of VPC peering.
- C. Correct.
Correct. The DNS peering zone needs to be created in VPC-A to allow VPC-B to access the private zone. This is part of the DNS peering configuration.
- D. Incorrect.
Incorrect. Sharing the private Cloud DNS zone is not an available option for enabling DNS peering between VPCs in Google Cloud.
- E. Incorrect.
Incorrect. A forwarding zone is not required for this scenario. DNS peering zones are the appropriate mechanism to enable DNS resolution between VPCs.