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 is deploying a multi-region Cross-Cloud Network using Network Connectivity Center (NCC) and pairs of multi-NIC Next-Generation Firewall (NGFW) virtual appliances in each region. Each NGFW has nic0 in a routing-vpc (connected to on-premises via Cloud Interconnect in NCC hub-1) and nic1 in a transit-vpc (connected to multiple workload-vpc networks in NCC hub-2).
Your routing topology must meet the following requirements:
workload-vpc to workload-vpc) and north-south (on-premises to workload-vpc) traffic through the NGFWs.Which configuration should you implement?
transit-vpc dynamic routing mode set to regional, replace the NCC Router appliance spokes with static routes pointing to the primary NGFW VM instance as the next hop, and connect the workload-vpc networks directly using VPC Network Peering.This approach limits Cloud Router route propagation to a single region, relies on manual static next-hop instance routes instead of dynamic BGP sessions, and establishes direct VPC Network Peering links between workload VPCs.
workload-vpc networks routes traffic directly between peered subnets, bypassing the centralized NGFWs.Your architecture existed strictly in a single region, direct communication between workload VPCs did not require NGFW inspection, and manual failover procedures were acceptable.
Even with IP forwarding (canIpForward) enabled on the NGFW VMs, static instance routes cannot provide the automated health-based withdrawal and multi-region failover delivered by BGP and global dynamic routing.
transit-vpc dynamic routing mode to global, configure hub-2 in a star topology with NGFW nic1 interfaces as Router appliance spokes in the center group, advertise a summarized supernet route for the workload-vpc ranges from nic1, and assign a lower BGP MED (such as 10) to the primary NGFW and a higher MED (such as 20) to the secondary NGFW in each region.This design deploys pairs of multi-NIC NGFWs as NCC Router appliance spokes bridging a routing-vpc (nic0) and a transit-vpc (nic1), combining BGP dynamic routing with NCC hub topologies to enforce centralized inspection and automated regional failover.
hub-2 as an NCC star topology isolates workload-vpc spokes in the edge group and places NGFW nic1 interfaces in the center group, eliminating direct spoke-to-spoke paths. Advertising a summarized supernet route covering all workload subnets from nic1 ensures inter-VPC traffic routes through the NGFWs.10) on the primary NGFW and a higher MED (20) on the secondary NGFW within each region forces Cloud Routers on both nic0 and nic1 to prefer the exact same active NGFW for both forward and return flows.transit-vpc (and routing-vpc) allows BGP routes to propagate across regions. Google Cloud automatically applies regional distance penalties to remote routes, keeping traffic local during normal operation while failing over to remote NGFWs if all local appliances fail.Combining an NCC star topology, summarized supernet BGP advertisements, global dynamic routing, and per-region BGP MEDs satisfies zero-bypass inspection, stateful symmetry, and multi-region resilience in a single native control plane.
transit-vpc, configure untagged policy-based routes (PBRs) in the transit-vpc pointing to the load balancer as the next hop without a skip-policy-based-route rule, and disable global access on the load balancers.This configuration attempts to steer traffic through internal passthrough Network Load Balancers using untagged policy-based routes (PBRs) in the transit-vpc while disabling global access and omitting skip-policy-based-route exceptions for the NGFW interfaces.
skip-policy-based-route rule applied to all NGFW interfaces, inspected packets immediately match the PBR again and loop back to the load balancer.hub-2) uses BGP dynamic route exchange rather than PBR-based next-hop load balancing.next-hop-other-routes) targeting all NVA interfaces are mandatory in PBR designs so post-inspection traffic follows standard VPC routing tables.You were using a PBR-driven single-NIC or multi-NIC load balancer architecture instead of NCC Router appliance spokes, included a skip-policy-based-route targeting all NGFW interfaces, and enabled global access on the load balancers.
Omitting skip-policy-based-route rules when deploying untagged PBRs in a transit VPC creates an infinite forwarding loop around the firewall appliances.
hub-2 in a mesh topology instead of a star topology, advertise individual workload-vpc subnet routes from nic1, and assign identical BGP MED values to both NGFWs in each region to distribute traffic evenly.Configuring an NCC mesh topology creates direct, any-to-any routing paths among all attached spokes, while assigning identical BGP Multi-Exit Discriminator (MED) values instructs Cloud Router to apply Equal-Cost Multi-Path (ECMP) forwarding across multiple appliances.
hub-2 allows workload-vpc spokes to exchange subnet routes and communicate directly with one another, bypassing the centralized NGFW appliances.nic1.nic1 is only effective at forcing transit when direct spoke-to-spoke routes are blocked by a star topology.Workload VPCs were allowed to communicate directly without Layer 7 inspection, and your NGFWs operated statelessly or used SNAT and session synchronization across active-active pairs.
To enforce centralized inspection across workload VPCs in NCC, hub-2 must use a star topology (with workload VPCs in the edge group and NGFWs in the center group) paired with unequal BGP MED values per region.
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