Google Professional Cloud Network Engineer Question 14
Single answerGoogle Cloud PlatformYour organization is migrating its applications to Google Cloud and needs to set up DNS for hybrid connectivity. The on-premises environment already has an authoritative DNS server. The organization wants to ensure that workloads running in Google Cloud can resolve on-premises hostnames and vice versa. Additionally, the solution must minimize the management overhead and be highly available. Which DNS topology should you implement?
- A
Set up a Cloud DNS managed private zone and manually update it with on-premises records.
- B
Use a Cloud DNS inbound server policy to forward DNS queries from Google Cloud to the on-premises DNS server.
- C
Configure a Cloud DNS outbound server policy to forward on-premises queries to Google Cloud DNS.
- D
Set up a Cloud DNS managed private zone and configure DNS peering between Cloud DNS and the on-premises DNS server.
Show answer and explanation
Correct answer: B
Explanation
To enable hybrid DNS resolution in a highly available and low-management-overhead manner, a Cloud DNS inbound server policy should be used. This allows DNS queries from workloads in Google Cloud to resolve on-premises hostnames by forwarding the queries to the on-premises DNS server. Other options either require manual maintenance, are not suitable for hybrid environments, or do not fulfill the requirements.
- A. Incorrect.
This option requires manually maintaining the DNS records in Cloud DNS, which increases management overhead and is not ideal for dynamic environments. It does not meet the requirement to minimize management overhead.
- B. Correct.
Using a Cloud DNS inbound server policy allows DNS queries from Google Cloud to be forwarded to the on-premises DNS server, enabling hybrid DNS resolution. This solution is highly available and minimizes management overhead.
- C. Incorrect.
An outbound server policy forwards queries from on-premises to Google Cloud DNS, which does not address the resolution of on-premises hostnames from Google Cloud.
- D. Incorrect.
DNS peering is designed for resolving DNS between two VPC networks within Google Cloud, not for on-premises environments. It is not applicable to this scenario.