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 connects its Google Cloud VPC network (prod-vpc) to an on-premises network via Cloud Interconnect and Cloud Router. You must implement outbound DNS resolution for Compute Engine VMs in prod-vpc to meet the following requirements:
corp.example.com. to primary on-premises BIND servers at 10.20.0.10 and 10.20.0.11.legacy.corp.example.com. directly to dedicated resolvers using carrier-grade NAT IP addresses (100.64.10.10 and 100.64.10.11) reachable over Cloud Interconnect, bypassing the primary BIND servers to reduce latency.*.internal) and public internet domains.Which configuration should you implement?
prod-vpc using standard routing: one for corp.example.com. targeting 10.20.0.10 and 10.20.0.11, and one for legacy.corp.example.com. targeting 100.64.10.10 and 100.64.10.11; advertise 35.199.192.0/19 from Cloud Router and allow TCP/UDP port 53 from 35.199.192.0/19 on the on-premises firewall.Standard routing is the default forwarding routing method in Cloud DNS. It inspects the IP address of each forwarding target and automatically decides whether to send DNS packets through the authorized VPC network or across the public internet based solely on whether the IP falls within RFC 1918 private address space.
100.64.10.10 and 100.64.10.11 belong to RFC 6598 (100.64.0.0/10), which is not RFC 1918 space. Under standard routing, Cloud DNS classifies these as Type 3 targets and attempts to send queries over the public internet instead of over Cloud Interconnect.prod-vpc has valid Cloud Router dynamic routes for 100.64.0.0/10 across Cloud Interconnect, standard routing ignores VPC routes for non-RFC 1918 IP addresses.SERVFAIL errors: Because private 100.64.10.10 and 100.64.10.11 servers are unreachable from the public internet, queries for legacy.corp.example.com. time out and return SERVFAIL.35.199.192.0/19 through the VPC network.--private-forwarding-targets or forwardingPath: "private") is mandatory for non-RFC 1918 private IPs or privately reused external IPs.This configuration would work if the legacy.corp.example.com. resolvers used RFC 1918 addresses (such as 10.x.x.x, 172.16.x.x, or 192.168.x.x) or if 100.64.10.10 and 100.64.10.11 were publicly routable internet IP addresses.
prod-vpc: one for corp.example.com. targeting 10.20.0.10 and 10.20.0.11 with standard routing, and one for legacy.corp.example.com. targeting 100.64.10.10 and 100.64.10.11 with private routing enabled; advertise 35.199.192.0/19 from Cloud Router and allow TCP/UDP port 53 from 35.199.192.0/19 on the on-premises firewall.Cloud DNS private forwarding zones enable suffix-based conditional forwarding from a VPC network to designated target name servers. Because forwarding zones are a specialized type of private zone, multiple overlapping domains can coexist on the same VPC network, and Cloud DNS routes queries using the longest matching domain suffix.
legacy.corp.example.com. over corp.example.com. due to longest-suffix matching, sending subdomain queries directly to 100.64.10.10 and 100.64.10.11 while directing all other corp.example.com. queries to 10.20.0.10 and 10.20.0.11.100.64.10.10 and 100.64.10.11 are RFC 6598 (non-RFC 1918) addresses, enabling private routing forces Cloud DNS to route those queries through prod-vpc over Cloud Interconnect rather than attempting public internet routing.*.internal) intact and resolving public domains directly without an on-premises hop.35.199.192.0/19 via Cloud Router and permitting TCP/UDP port 53 on the on-premises firewall ensures queries reach the resolvers and responses return to prod-vpc.169.254.169.254) without guest OS modifications.Unlike an outbound server policy, overlapping forwarding zones provide granular domain-level conditional routing, support private non-RFC 1918 targets over hybrid links, and maintain native high-performance resolution for internal and internet domains.
prod-vpc: one for corp.example.com. targeting 10.20.0.10 and 10.20.0.11, and one for legacy.corp.example.com. targeting 100.64.10.10 and 100.64.10.11 with private routing enabled; enable an inbound DNS server policy on prod-vpc so outbound queries use prod-vpc subnet IPs, and allow TCP/UDP port 53 from the prod-vpc subnet range on the on-premises firewall.A Cloud DNS inbound server policy reserves internal inbound forwarder IP addresses within each subnet of a VPC network so that on-premises clients and DNS servers can send queries into Google Cloud to resolve Cloud DNS private zones, peering zones, and Compute Engine internal DNS names.
35.199.192.0/19, not from the prod-vpc subnet ranges.35.199.192.0/19): Without advertising 35.199.192.0/19 from Cloud Router to the on-premises network, on-premises DNS servers have no route back to Cloud DNS, causing response packets to drop.prod-vpc subnet IP ranges on the on-premises firewall drops incoming DNS queries sourced from 35.199.192.0/19, resulting in SERVFAIL errors.DNS_RESOLVER and operate independently of outbound forwarding zones.35.199.192.0/19 to traverse a Cloud Interconnect VLAN attachment or Cloud VPN tunnel back to the same originating VPC network.Enabling an inbound DNS server policy and permitting VPC subnet ranges on-premises would be required if the goal were inbound DNS resolution—allowing on-premises hosts to query records hosted inside Cloud DNS private zones—rather than outbound forwarding from Google Cloud VMs.
prod-vpc specifying 10.20.0.10 and 10.20.0.11 as alternative name servers, configure conditional forwarders on those BIND servers for legacy.corp.example.com. pointing to 100.64.10.10 and 100.64.10.11, and advertise 35.199.192.0/19 via Cloud Router.A Cloud DNS outbound server policy configures an alternative name server for an entire VPC network. When enabled, all DNS queries generated by Compute Engine VMs in that VPC network are redirected to the specified on-premises or external DNS servers rather than being resolved locally by Cloud DNS.
prod-vpc from resolving Compute Engine internal DNS (*.internal), Cloud DNS private zones, forwarding zones, and peering zones.legacy.corp.example.com. queries through the primary BIND servers first rather than directly to 100.64.10.10 and 100.64.10.11 fails the requirement to bypass the BIND servers and minimize latency.35.199.192.0/19 (or outbound endpoints) for transport.This approach would be appropriate only if organizational security policy mandated that 100% of VPC DNS traffic—including public internet queries—be inspected, logged, or filtered by on-premises resolvers, and local Compute Engine internal DNS resolution was not required.
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