Google Professional Cloud Network Engineer Question 563
Select 2Google Cloud PlatformYou are working for an organization that has two separate Google Cloud projects: Project A and Project B. Project A hosts a private DNS zone for the domain internal.example.com, while Project B requires access to resolve DNS queries for this domain. You decide to set up DNS peering to enable this functionality. Which of the following steps must you perform to successfully establish DNS peering between the two projects?
- A
Create a DNS peering zone in Project B that points to the private DNS zone in Project A.
- B
Ensure that the VPC networks in Project A and Project B are peered.
- C
Grant the
roles/dns.peerIAM role to the appropriate service accounts in both projects. - D
Create a private DNS forwarding zone in Project A and configure it to forward queries to Project B.
- E
Add the necessary DNS policies to Project B's VPC to allow DNS resolution from Project A.
Show answer and explanation
Correct answers: A, B
Explanation
To enable DNS peering between two Google Cloud projects, you must create a DNS peering zone in the project that requires access to the private DNS zone. Additionally, the VPC networks in both projects must be peered to allow DNS traffic to flow between them. Other options, such as using DNS forwarding zones or specific IAM roles, are not relevant to DNS peering in Google Cloud.
- A. Correct.
Correct. A DNS peering zone must be created in Project B to reference the private DNS zone in Project A.
- B. Correct.
Correct. VPC network peering is required to enable communication between the projects for DNS queries.
- C. Incorrect.
Incorrect. There is no
roles/dns.peerIAM role required for setting up DNS peering in Google Cloud. - D. Incorrect.
Incorrect. A private DNS forwarding zone is not needed for DNS peering; instead, a DNS peering zone is used.
- E. Incorrect.
Incorrect. DNS policies are not required for DNS peering. The DNS peering zone and VPC network peering handle the necessary resolution.