nerdexam
Google

PROFESSIONAL-CLOUD-NETWORK-ENGINEER · Question #140

You are designing a hybrid cloud environment. Your Google Cloud environment is interconnected with your on-premises network using HA VPN and Cloud Router in a central transit hub VPC. The Cloud Router

The correct answer is A. Create a private forwarding zone in Cloud DNS for `corp.altostrat.com' called corp-altostrat-com. To enable Compute Engine resources in spoke VPCs to resolve on-premises private hostnames via Cloud DNS while also resolving Google Cloud hostnames, create a private forwarding zone in Cloud DNS pointing to the on-premises DNS server, scoped to the relevant VPCs.

Submitted by noor.lb· Apr 18, 2026Designing, planning, and prototyping a Google Cloud network

Question

You are designing a hybrid cloud environment. Your Google Cloud environment is interconnected with your on-premises network using HA VPN and Cloud Router in a central transit hub VPC. The Cloud Router is configured with the default settings. Your on-premises DNS server is located at 192.168.20.88. You need to ensure that your Compute Engine resources in multiple spoke VPCs can resolve on-premises private hostnames using the domain corp.altostrat.com while also resolving Google Cloud hostnames. You want to follow Google-recommended practices. What should you do?

Options

  • ACreate a private forwarding zone in Cloud DNS for `corp.altostrat.com' called corp-altostrat-com
  • BCreate a private forwarding zone in Cloud DNS for `corp.altostrat.com' called corp-altostrat-com
  • CCreate a private forwarding zone in Cloud DNS for `corp.altostrat.com' called corp-altostrat-com
  • DCreate a private forwarding zone in Cloud DNS for `corp altostrat.com' called corp-altostrat-com

How the community answered

(25 responses)
  • A
    76% (19)
  • B
    12% (3)
  • C
    8% (2)
  • D
    4% (1)

Why each option

To enable Compute Engine resources in spoke VPCs to resolve on-premises private hostnames via Cloud DNS while also resolving Google Cloud hostnames, create a private forwarding zone in Cloud DNS pointing to the on-premises DNS server, scoped to the relevant VPCs.

ACreate a private forwarding zone in Cloud DNS for `corp.altostrat.com' called corp-altostrat-comCorrect

Creating a private forwarding zone in Cloud DNS for `corp.altostrat.com` that points to the on-premises DNS server (192.168.20.88) is the recommended Google Cloud practice for hybrid DNS resolution. This configuration allows resources in the authorized Google Cloud VPCs (including peered spoke VPCs) to query the on-premises DNS server for records within the `corp.altostrat.com` domain, while Google Cloud's internal DNS automatically handles resolution for Google Cloud hostnames.

BCreate a private forwarding zone in Cloud DNS for `corp.altostrat.com' called corp-altostrat-com

This choice is a duplicate of A, hence also correct in principle, but A is the specified answer.

CCreate a private forwarding zone in Cloud DNS for `corp.altostrat.com' called corp-altostrat-com

This choice is a duplicate of A, hence also correct in principle, but A is the specified answer.

DCreate a private forwarding zone in Cloud DNS for `corp altostrat.com' called corp-altostrat-com

This choice is a duplicate of A, hence also correct in principle, but A is the specified answer.

Concept tested: Cloud DNS private forwarding zones for hybrid DNS

Source: https://cloud.google.com/dns/docs/zones#private_forwarding_zones

Topics

#Cloud DNS#Hybrid DNS#VPC Networking#DNS Resolution

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PROFESSIONAL-CLOUD-NETWORK-ENGINEER Practice