Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization has connected its on-premises data center to a Google Cloud VPC network using Dedicated Interconnect and Cloud Router. You need to implement bidirectional hybrid DNS resolution with the following requirements:
corp.example.com while retaining access to Compute Engine internal DNS and Cloud DNS private zones.gcp.example.com.Which architecture should you implement?
corp.example.com targeting the on-premises DNS servers, and enable an inbound DNS server policy on the VPC network. Configure Cloud Router in custom advertisement mode to advertise only 35.199.192.0/19 without VPC subnet ranges, allow TCP/UDP port 53 from 35.199.192.0/19 on the on-premises firewall, and configure conditional forwarding for gcp.example.com on-premises to the inbound forwarder IP addresses.When Cloud Router is switched from default advertisement mode to custom advertisement mode, it stops automatically announcing VPC subnet IP ranges unless you explicitly enable Advertise all subnets visible to the Cloud Router or include those prefixes manually. Advertising only 35.199.192.0/19 removes VPC subnet prefixes from the BGP routing table sent to on-premises routers.
gcp.example.com from on-premises: Fails because Cloud DNS allocates inbound forwarder entry point IP addresses directly from the primary IPv4 address ranges of the subnets in the VPC network. If VPC subnet ranges (or the specific inbound forwarder IP addresses) are omitted from Cloud Router's custom BGP advertisements, on-premises DNS servers have no route to reach the inbound forwarder entry points over Dedicated Interconnect.35.199.192.0/19 is properly advertised.Cloud Router's custom advertisement configuration also included all visible VPC subnets (or explicitly advertised the specific inbound forwarder IP addresses) alongside 35.199.192.0/19.
corp.example.com targeting the on-premises DNS servers, and enable an inbound DNS server policy on the VPC network. Configure Cloud Router with custom route advertisements for 35.199.192.0/19 plus VPC subnets, allow TCP/UDP port 53 from 35.199.192.0/19 on the on-premises firewall, and configure conditional forwarding for gcp.example.com on-premises to the inbound forwarder IP addresses.Combining a Cloud DNS private forwarding zone with an inbound DNS server policy establishes two-way name resolution between Google Cloud and on-premises environments while keeping each environment authoritative for its own domains. Cloud Router custom route advertisements and aligned firewall rules ensure both outbound queries and inbound queries have valid Layer 3 paths.
corp.example.com while retaining internal DNS and private zones: A private forwarding zone matches only queries ending in corp.example.com using longest suffix matching. Queries for gcp.example.com, Compute Engine .internal names, and public domains continue to resolve natively through Cloud DNS without leaving Google Cloud.gcp.example.com from on-premises: Enabling an inbound DNS server policy allocates inbound forwarder IP addresses from the primary IPv4 range of each subnet in the VPC network. Configuring conditional forwarding on the on-premises DNS servers routes gcp.example.com lookups to those regional entry point IPs.35.199.192.0/19 alongside all VPC subnet ranges ensures on-premises routers can reach both the inbound forwarder IPs and return traffic for 35.199.192.0/19. Allowing TCP/UDP port 53 from 35.199.192.0/19 on the on-premises firewall permits forwarded Cloud DNS queries.169.254.169.254 without custom /etc/resolv.conf or DHCP edits.gcp.example.com.Unlike an outbound server policy with alternative name servers, a forwarding zone preserves Compute Engine internal DNS and Cloud DNS private zones. Unlike default BGP advertisement, custom route advertisement explicitly propagates 35.199.192.0/19 while preserving subnet reachability for inbound forwarder entry points.
corp.example.com targeting the on-premises DNS servers, and enable an inbound DNS server policy on the VPC network. Leave Cloud Router in default route advertisement mode, allow TCP/UDP port 53 from the VPC subnet CIDR ranges on the on-premises firewall, and configure conditional forwarding for gcp.example.com on-premises to the inbound forwarder IP addresses.When Cloud Router operates in default advertisement mode, its Border Gateway Protocol (BGP) sessions automatically advertise the primary and secondary IP ranges of VPC subnets to the on-premises router. However, it does not automatically advertise special Google-managed proxy ranges used by Cloud DNS outbound forwarding.
35.199.192.0/19): Fails because Cloud DNS sends outbound-forwarded queries to on-premises DNS servers using source IP addresses from 35.199.192.0/19, not from the VPC's RFC 1918 subnet ranges. Without a custom advertised route for 35.199.192.0/19 on Cloud Router (or an equivalent on-premises static route), on-premises routers have no return path to route DNS responses back to the VPC network's Dedicated Interconnect VLAN attachment.35.199.192.0/19.35.199.192.0/19 over UDP and TCP port 53.SERVFAIL errors on Google Cloud VMs.Static routes for 35.199.192.0/19 were manually configured on all on-premises routers pointing to the Dedicated Interconnect next hops and the on-premises firewall permitted 35.199.192.0/19 instead of only VPC subnet CIDRs.
35.199.192.0/19 plus VPC subnets, allow TCP/UDP port 53 from 35.199.192.0/19 on the on-premises firewall, and configure conditional forwarding for gcp.example.com on-premises to the inbound forwarder IP addresses.A Cloud DNS server policy with alternative name servers defines an outbound DNS server policy for a VPC network. Instead of relying on Cloud DNS's default VPC name resolution order, Cloud DNS intercepts all DNS queries sent by VM instances to the metadata server (169.254.169.254) and forwards every query to the specified alternative name servers.
gcp.example.com), forwarding zones, peering zones, or Compute Engine internal DNS zones (.internal), unless the queries match a GKE cluster-scoped zone or response policy.corp.example.com: Fails because alternative name servers redirect all DNS traffic rather than selectively forwarding only queries for corp.example.com.Your organization had a strict security requirement to inspect, filter, or monitor every single DNS query from Google Cloud VMs on-premises (and private DNS logging could not satisfy that requirement), rather than preserving local resolution for Cloud DNS private zones and Compute Engine internal DNS.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated