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 VPC network (corp-vpc) has subnets in us-central1 and us-east1, with three static routes to 192.168.50.0/24 at priority 100 targeting next hops in us-central1:
route-ilb: Internal passthrough Network Load Balancer ilb-nva (global access disabled)route-vm: VM instance vm-nva (--can-ip-forward enabled)route-vpn: Classic VPN tunnel vpn-backupTraffic currently load-balances across vm-nva and vpn-backup, ignoring ilb-nva. When both backup next hops go down, us-east1 traffic is dropped. You need both regions to prefer ilb-nva, fall back to vm-nva if route-ilb is removed, and fail over to vpn-backup if vm-nva stops.
What should you do?
ilb-nva forwarding rule. Delete all three static routes and recreate them for 192.168.50.0/24 with priority 300 for route-ilb, priority 200 for route-vm, and priority 100 for route-vpn.This approach enables global access on the internal passthrough Network Load Balancer forwarding rule and replaces the existing static routes with distinct priority numbers (300, 200, and 100). However, it assigns the numerical priorities in reverse order of the desired traffic path.
In Google Cloud VPC routing, lower numerical values represent higher priorities, where 0 is the highest possible priority and 65535 is the lowest. Because route-vpn is assigned priority 100:
200 and 300) before evaluating preference categories. As a result, all traffic to 192.168.50.0/24 is routed immediately over vpn-backup instead of ilb-nva.vpn-backup loses its IKE security association, traffic fails over to vm-nva (priority 200) rather than using ilb-nva (priority 300).vpn-backup or vm-nva remains operational, ilb-nva never receives traffic.0 (highest) to 65535 (lowest), while dynamic routes created by Cloud Router begin at 65536.This configuration would work only if the priority numbers were reversed so that route-ilb used 100, route-vm used 200, and route-vpn used 300, or if the organization intentionally wanted vpn-backup to serve as the primary egress path.
corp-vpc to global. Update the existing static routes in place to assign priority 100 to route-ilb, priority 200 to route-vm, and priority 300 to route-vpn.This option changes the VPC network's dynamic routing mode from regional to global and attempts to modify the priorities of the existing static routes in place without recreating them.
This approach fails on two fundamental Google Cloud networking behaviors:
global only allows Cloud Router dynamic routes (learned via BGP) to be programmed across all regions. It has no effect on custom static routes that target an internal passthrough Network Load Balancer. Unless global access is explicitly enabled on the load balancer's forwarding rule, packets sent from us-east1 to route-ilb in us-central1 are still dropped.| Setting | Scope | Effect on us-east1 access to ilb-nva in us-central1 |
|---|---|---|
VPC dynamic routing mode: global | Cloud Router BGP routes | None; ilb-nva remains reachable only in us-central1 |
ILB forwarding rule: global access enabled | Internal passthrough NLB VIP & next-hop routes | ilb-nva becomes reachable from all regions in corp-vpc |
Dynamic HA VPN BGP routing were being used across regions instead of static routes, and --allow-global-access were enabled on ilb-nva alongside deleting and recreating the static routes with distinct priorities.
ilb-nva forwarding rule. Delete all three static routes and recreate them for 192.168.50.0/24 with priority 100 for route-ilb, priority 200 for route-vm, and priority 300 for route-vpn.This solution enables global access on the ilb-nva forwarding rule and recreates all three static routes with strictly ordered priorities (100 for route-ilb, 200 for route-vm, and 300 for route-vpn). Because static route priorities cannot be modified in place after creation, deleting and recreating the routes is required to apply the new priority values.
100. In the Google Cloud routing order, after filtering by priority, Google Cloud selects only the most favorable preference category. Next-hop VM instances and Classic VPN tunnels are in the first preference category, whereas internal passthrough Network Load Balancers are in the third choice category. Consequently, route-ilb was ignored and ECMP ran across vm-nva and vpn-backup. By assigning priority 100 exclusively to route-ilb, lower-priority routes (200 and 300) are discarded during the disregard low priority routes step before preference categories are ever evaluated.--allow-global-access on the ilb-nva forwarding rule allows VMs in us-east1 to reach the load balancer next hop in us-central1. Without global access, packets from other regions hitting a load balancer next-hop route are dropped.route-ilb is deleted for maintenance, route-vm (priority 200) becomes the highest-priority route. If vm-nva is stopped or deleted, Google Cloud disregards route-vm during the disregard unusable next hops step (which occurs before priority comparison) and automatically routes traffic over route-vpn (priority 300), provided vpn-backup has an active Phase 1 IKE security association.ilb-nva next-hop reachability across every region in corp-vpc.Using distinct priorities on the exact 192.168.50.0/24 prefix leverages Google Cloud's native routing order cleanly, avoiding prefix-overlap hazards while guaranteeing predictable active-passive failover across heterogeneous next-hop targets.
ilb-nva forwarding rule. Keep priority 100 on all routes, but recreate route-ilb with destination 192.168.50.0/24, route-vm with 192.168.48.0/22, and route-vpn with 192.168.0.0/16.This approach enables global access on the ilb-nva forwarding rule and attempts to enforce path preference using longest-prefix match (192.168.50.0/24 > 192.168.48.0/22 > 192.168.0.0/16) while keeping every route at priority 100.
Although 192.168.50.0/24 initially directs traffic to ilb-nva, this design breaks automatic failover when vm-nva stops:
route-ilb is removed and vm-nva is subsequently stopped, Google Cloud first selects 192.168.48.0/22 (route-vm) because it is more specific than 192.168.0.0/16 (route-vpn), discarding route-vpn from the route model. In the later step, Google Cloud disregards route-vm because vm-nva is stopped, leaving the route model empty and dropping all packets instead of failing over to vpn-backup.192.168.48.0/22 and 192.168.0.0/16) capture traffic destined for other networks within those ranges that are not covered by local subnet routes.100, they sacrifice resilience.No failover between vm-nva and vpn-backup were required and the broader CIDR ranges (192.168.48.0/22 and 192.168.0.0/16) were exclusively dedicated to those respective backup paths.
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