Examkin

Question

Difficulty: MediumPlanning Network Load Balancing, Cloud DNS, and Cloud CDN

An enterprise is establishing hybrid connectivity between an on-premises data center and a Google Cloud Virtual Private Cloud (VPC) network via Cloud Interconnect. Compute Engine virtual machines deployed in the VPC must resolve hostnames in the internal domain internal.company.com, which are managed by on-premises DNS servers. The architecture requires DNS queries for internal.company.com originating from VPC workloads to be routed to the on-premises DNS servers without exposing internal domain data to the public internet. Which Cloud DNS configuration should you plan to meet these requirements?

  1. Create a Cloud DNS private zone for internal.company.com configured for DNS forwarding, specifying the on-premises DNS server IP addresses as forwarding targets.Answer
  2. B
    Create a Cloud DNS public zone for internal.company.com containing NS records that point to the public IP addresses of the on-premises DNS servers.
  3. C
    Deploy an External HTTP(S) Load Balancer configured with backend service endpoints pointing to the on-premises DNS server IP addresses over TCP port 53.
  4. D
    Create a Cloud DNS private zone for internal.company.com and enable Cloud CDN caching to cache DNS query responses locally within the VPC.

Answer

Create a Cloud DNS private zone for internal.company.com configured for DNS forwarding, specifying the on-premises DNS server IP addresses as forwarding targets.
Configuring a Cloud DNS private zone with DNS outbound forwarding allows Virtual Private Cloud (VPC) instances to forward domain lookup requests for internal.company.com directly to specified on-premises DNS server IP addresses over private network connections (such as Cloud Interconnect or Cloud VPN). This meets all requirements for private, secure, and seamless hybrid name resolution.

Step-by-Step Solution

1
Analyze the networking scope and protocol requirements
The requirement asks for private DNS resolution of an internal domain (internal.company.com) from GCP VPC VMs to on-premises DNS servers over Cloud Interconnect.
Traffic must remain private within the hybrid network and DNS resolution must be natively handled for VPC workloads.
2
Evaluate Google Cloud DNS capabilities for hybrid networks
Cloud DNS private zones support outbound DNS forwarding, allowing queries for specific domain suffixes to be sent to target IP addresses across Cloud Interconnect or VPN.
This bridges VPC DNS resolution with on-premises infrastructure securely without internet exposure.
3
Eliminate incompatible service options
Public DNS zones expose data publicly, Layer 7 HTTP(S) Load Balancers do not support DNS protocol, and Cloud CDN cannot be attached to Cloud DNS.
Selecting service types aligned with Layer 3/Layer 7 boundaries and service capabilities ensures proper architecture.

Key Concept

Cloud DNS Private Zone Forwarding for Hybrid Architecture
Rate this question

Topics

Planning Network Load Balancing, Cloud DNS, and Cloud CDN

More questions from this topic