Google Professional Cloud Network Engineer Question 161
Select 3Google Cloud PlatformYour company manages two separate Google Cloud environments: one for production and another for development. Each environment uses its own VPC network. The production VPC hosts a Cloud DNS private zone for 'internal.prod.example.com', and the development VPC hosts a Cloud DNS private zone for 'internal.dev.example.com'. You need to configure DNS so that instances in the production VPC can resolve 'internal.dev.example.com' and instances in the development VPC can resolve 'internal.prod.example.com'. What should you do?
- A
Create DNS peering zones in both the production and development VPCs and configure them to forward DNS queries to each other's private zones.
- B
Set up a DNS forwarding rule in the production VPC to forward requests for 'internal.dev.example.com' to the development VPC's private zone.
- C
Set up a DNS forwarding rule in the development VPC to forward requests for 'internal.prod.example.com' to the production VPC's private zone.
- D
Use VPC Network Peering between the production and development VPCs to enable DNS resolution between the private zones automatically.
- E
Configure a hybrid DNS solution where Cloud DNS is integrated with an on-premises DNS server to manage all internal DNS resolutions.
Show answer and explanation
Correct answers: A, B, C
Explanation
To enable DNS resolution between private zones in two separate VPC networks, you need to explicitly configure DNS peering zones and forwarding rules. DNS peering zones allow DNS queries to traverse VPC boundaries, and forwarding rules ensure that queries for specific domains are directed to the correct private zone. VPC Network Peering alone does not handle DNS, and hybrid DNS solutions are unnecessary when Cloud DNS can address the requirements directly.
- A. Correct.
Correct: DNS peering zones allow you to resolve private DNS records across VPC networks by explicitly peering DNS zones. You need to create peering zones in both directions for bidirectional resolution.
- B. Correct.
Correct: A DNS forwarding rule is necessary to forward requests for 'internal.dev.example.com' from the production VPC to the development VPC's private zone.
- C. Correct.
Correct: Similarly, a DNS forwarding rule is required to forward requests for 'internal.prod.example.com' from the development VPC to the production VPC's private zone.
- D. Incorrect.
Incorrect: VPC Network Peering enables network connectivity between VPCs but does not automatically handle DNS resolution between private zones. Additional DNS configuration is still required.
- E. Incorrect.
Incorrect: While a hybrid DNS solution can handle complex DNS resolution requirements, it is unnecessary for this scenario as Cloud DNS can natively solve the problem with DNS peering and forwarding configurations.