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 hub-vpc connects to on-premises via Dedicated Interconnect in us-central1 and peers with spoke-vpc (us-central1 and us-east1 subnets). Current Cloud DNS configuration:
hub-vpc: inbound server policy and outbound forwarding zone for corp.example.com.spoke-vpc: DNS peering zone for corp.example.com. targeting hub-vpc, plus a private zone for app.gcp.example.com.Validation results:
spoke-vpc VMs in us-east1 time out querying corp.example.com, while us-central1 VMs succeed.dig api.app.gcp.example.com @<inbound-forwarder-ip> returns NXDOMAIN from hub-vpc, but times out from on-premises (ping to a hub-vpc VM succeeds).Which set of actions resolves all failures and validates end-to-end resolution?
spoke-vpc, configure zone transfers on app.gcp.example.com. to on-premises DNS servers, add a hub-vpc VPC ingress allow rule for TCP/UDP port 53, and verify with dig.An outbound DNS server policy with an alternative name server redirects all DNS queries from a VPC network to specified external resolvers, while DNS zone transfers (AXFR/IXFR) replicate DNS zone records between traditional authoritative DNS servers.
app.gcp.example.com. records with on-premises DNS servers.spoke-vpc to on-premises DNS servers via an alternative name server still sends queries from 35.199.192.0/19, which cannot traverse the VPC Network Peering connection to hub-vpc's Interconnect.hub-vpc for port 53 does not resolve timeouts caused by the on-premises firewall blocking outbound port 53 traffic to the hub-vpc inbound forwarder IP.GLOBAL routing constraint: Even when routed via hub-vpc, consumer VMs in us-east1 still require GLOBAL dynamic routing on hub-vpc.You replaced Cloud DNS private zones with self-managed BIND servers on Compute Engine VMs that support zone transfers and deployed direct hybrid connectivity to spoke-vpc where all DNS traffic must be inspected on-premises.
spoke-vpc, enable custom route import on spoke-vpc peering, advertise 35.199.192.0/19 from a new Cloud Router in us-east1 in hub-vpc, and verify with dig.An inbound DNS server policy allocates internal forwarder IP addresses within a specific VPC's subnets to accept queries from connected networks, while a Cloud Router advertises VPC and custom IP prefixes over BGP sessions attached to hybrid links.
spoke-vpc lacks direct hybrid connectivity and VPC Network Peering is non-transitive, on-premises clients cannot reach an inbound forwarder IP allocated in spoke-vpc via hub-vpc, nor are their conditional forwarders targeting spoke-vpc.us-east1 lacks a hybrid attachment: Advertising 35.199.192.0/19 from a Cloud Router in us-east1 has no effect without a VLAN attachment or VPN tunnel in us-east1; under REGIONAL dynamic routing, us-east1 VMs in spoke-vpc still fail to use hub-vpc's us-central1 Interconnect.hub-vpc's inbound forwarder IP.GLOBAL dynamic routing on the producer VPC or a hybrid connection in the same region as the consumer VM.spoke-vpc had its own Dedicated Interconnect attachment in us-central1, on-premises conditional forwarders pointed to spoke-vpc's inbound forwarder IP with port 53 allowed, and hub-vpc had a VLAN attachment in us-east1.
hub-vpc dynamic routing mode to GLOBAL, create a DNS peering zone for app.gcp.example.com. in hub-vpc targeting spoke-vpc, permit UDP/TCP port 53 on the on-premises firewall to the inbound forwarder IP, and verify resolution from both environments using dig.Combining Cloud DNS peering zones, GLOBAL dynamic routing mode, and properly configured on-premises firewall rules establishes bidirectional name resolution across a hub-and-spoke VPC topology connected to an on-premises network.
us-east1 outbound forwarding timeouts: Changing hub-vpc dynamic routing mode from REGIONAL to GLOBAL enables the producer VPC network (hub-vpc) to route DNS queries originating from consumer VPC (spoke-vpc) VMs in us-east1 across the Dedicated Interconnect attachment in us-central1.NXDOMAIN from the hub-vpc inbound forwarder: Creating a Cloud DNS peering zone for app.gcp.example.com. in hub-vpc targeting spoke-vpc extends visibility so the inbound DNS server policy forwarder in hub-vpc can resolve private zones hosted in spoke-vpc.hub-vpc inbound forwarder IP permits conditional-forwarded queries to reach Google Cloud, as ping already proved Layer 3 reachability is intact.dig from on-premises against the hub-vpc inbound forwarder IP and running dig @169.254.169.254 from a us-east1 VM in spoke-vpc confirms both paths via the metadata server.35.199.192.0/19 in a single hub-vpc to prevent return-routing ambiguity.Unlike configuring outbound forwarding in every spoke VPC or attempting unsupported zone transfers, this design follows Google Cloud's hub-and-spoke DNS architecture, avoids asymmetric return-route conflicts, and resolves all three root causes cleanly.
corp.example.com. directly in spoke-vpc, add hub-vpc VPC ingress firewall rules for 35.199.192.0/19, and re-test with dig.Exporting custom routes over VPC Network Peering shares dynamically learned BGP routes between directly peered VPCs, while an outbound forwarding zone directs DNS queries for a specified domain from an authorized VPC to target name servers.
spoke-vpc cannot forward DNS queries across its VPC peering connection to hub-vpc to reach on-premises DNS servers.app.gcp.example.com.: Neither custom route exchange nor a spoke-vpc forwarding zone grants hub-vpc visibility into spoke-vpc's private zone, so the hub-vpc inbound forwarder still returns NXDOMAIN.35.199.192.0/19 firewall rules: Adding a VPC ingress rule in hub-vpc for 35.199.192.0/19 is ineffective because 35.199.192.0/19 is the source range used by Cloud DNS for outbound queries to on-premises, and it does not unblock port 53 egress on the on-premises firewall.35.199.192.0/19 egress proxy range across all VPCs, causing return-traffic routing ambiguity if multiple VPCs perform outbound forwarding independently.spoke-vpc had its own dedicated Cloud Interconnect or Cloud VPN connection directly to a separate on-premises environment, hub-vpc already had a DNS peering zone targeting spoke-vpc, and on-premises firewalls already permitted traffic to the inbound forwarder IP.
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