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 uses a hub-and-spoke VPC topology (hub-vpc peered with spoke1-vpc and spoke2-vpc) with multi-NIC firewall virtual appliances deployed in hub-vpc (nic0) and dmz-vpc (nic1). In hub-vpc, you deployed two internal passthrough Network Load Balancers using TCP port 80 forwarding rules and CLIENT_IP session affinity: ilb-central (10.10.0.10 in us-central1) and ilb-east (10.10.1.10 in us-east1).
You must implement routing to meet these requirements:
0.0.0.0/0) only from VMs in spoke1-vpc tagged inspected-workload.ilb-central for all traffic and allow regional failover to ilb-east across any region when the primary route is removed.How should you configure the load balancers and routes?
Global dynamic routing mode controls how Cloud Routers propagate learned BGP routes across regions within a VPC network. Meanwhile, referencing a load balancer next hop by forwarding rule name and region (--next-hop-ilb with --next-hop-ilb-region) is one of the CLI methods for defining a static route next hop.
ilb-central and ilb-east reside in hub-vpc, routes in spoke1-vpc cannot reference them by name; you must specify their forwarding rule IP addresses instead.us-central1 to ilb-east during regional failover (or from any remote region to ilb-central) are dropped—regardless of whether the VPC's dynamic routing mode is set to global.--allow-global-access is mandatory whenever cross-region clients or regional failover routes must reach a next-hop load balancer.The routes were created in hub-vpc (matching the load balancers' VPC network) AND clients were strictly confined to the same region as their respective load balancer with no cross-region failover requirement.
An L3_DEFAULT forwarding rule enables a standalone internal passthrough Network Load Balancer to accept multiple IP protocols (such as TCP, UDP, ICMP, and ESP) on a single virtual IP address. Separately, equal-priority static routes in a VPC network are commonly associated with Equal-Cost Multipath (ECMP) load distribution across standard next-hop VM instances.
L3_DEFAULT: A load balancer whose forwarding rule uses the L3_DEFAULT protocol cannot be used as the next hop for a static route. If such a route is created, Google Cloud silently drops all traffic matching the route.800) but point to different next-hop load balancers, Google Cloud picks only one load balancer via an internal algorithm without consistency guarantees and fails to establish a deterministic primary/failover preference for ilb-central.TCP or UDP forwarding rule already passes all IP protocols when invoked via a static route; L3_DEFAULT is unnecessary and unsupported.800 and 900) to enforce a deterministic primary path and secondary failover path.No scenario makes this valid for next-hop routing because L3_DEFAULT forwarding rules always cause silent drops as static route next hops, and equal-priority routes to distinct next-hop load balancers never provide ECMP or deterministic preference.
An internal passthrough Network Load Balancer can serve as the next hop in a custom VPC static route to distribute traffic across a pool of healthy multi-NIC virtual appliances (such as firewalls or routers) in a bump-in-the-wire architecture. When used as a route next hop, the load balancer forwards packets directly to backend appliances with original source and destination IP addresses preserved.
--tags=inspected-workload routes must be created directly inside spoke1-vpc. Specifying each load balancer's forwarding rule IP address (10.10.0.10 and 10.10.1.10) in --next-hop-ilb allows a static route in spoke1-vpc to point to load balancers residing in the peered hub-vpc.800 to ilb-central and priority 900 to ilb-east ensures all tagged traffic prefers ilb-central first and transitions to ilb-east if the priority 800 route is removed. Enabling global access (--allow-global-access) on both forwarding rules ensures VMs in any region of spoke1-vpc can reach either regional next-hop load balancer without packets being dropped.TCP:80) only govern standalone load-balanced traffic—the next-hop route automatically forwards TCP, UDP, ICMP, and other supported IP protocols. Using CLIENT_IP session affinity preserves symmetric hashing across the multi-NIC appliances without requiring SNAT.spoke1-vpc require no internal routing configuration.inspected-workload tag match the 0.0.0.0/0 routes, leaving untagged workloads unaffected.This design adheres to every Google Cloud VPC peering, tagging, protocol, and cross-region scope constraint while providing clean primary/backup traffic steering to multi-NIC appliances in a shared hub network.
VPC Network Peering allows connected VPC networks to exchange custom static and dynamic routes when the exporting network enables custom route export and the importing network enables custom route import. For untagged static routes using an internal passthrough Network Load Balancer next hop, this mechanism propagates hub-level inspection routes to spoke VPCs.
hub-vpc carry --tags=inspected-workload, spoke1-vpc will never import them.spoke1-vpc, tagged VMs in spoke1-vpc will fall back to their local default internet gateway or existing VPC routes, bypassing the firewall appliances completely.hub-vpc works only when all workloads in the importing spoke VPC can share an untagged route.All VMs in spoke1-vpc (not just VMs with a specific network tag) needed their 0.0.0.0/0 traffic routed through hub-vpc appliances, allowing you to create untagged static routes in hub-vpc and export them over VPC Network Peering.
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