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 manages a hub-and-spoke topology in Google Cloud using VPC Network Peering with the following configuration:
transit-vpc (currently set to Regional dynamic routing mode) connects to an on-premises network (192.168.44.0/24) via Dedicated Interconnect VLAN attachments in us-west1 (west-a with MED 10, west-b with MED 20) and us-east1 (east-a with MED 10, east-b with MED 20). Its Cloud Routers use Default route advertisement mode and the peering links export custom routes.workload-vpc (currently set to Global dynamic routing mode) has subnets in us-west1, us-central1, and us-east1, and imports custom routes from transit-vpc.eu-isolated-vpc has a single subnet in europe-west1 and imports custom routes from transit-vpc.You need workloads in us-central1 of workload-vpc to reach 192.168.44.0/24 over the lowest-cost cross-region path, allow on-premises hosts to reach all workload-vpc subnets, and prevent eu-isolated-vpc from receiving any dynamic routes for 192.168.44.0/24 while maintaining internal subnet connectivity to transit-vpc.
Which configuration change should you implement?
This option switches transit-vpc to Global dynamic routing mode, leaves its Cloud Routers in Default route advertisement mode, and attempts to isolate eu-isolated-vpc by changing eu-isolated-vpc to Regional dynamic routing mode.
workload-vpc: With Default advertisement mode, Cloud Routers in transit-vpc advertise only subnet routes located inside transit-vpc across all regions. They do not advertise subnet routes learned through VPC Network Peering from workload-vpc, leaving on-premises routers without return paths to workload-vpc.eu-isolated-vpc: When transit-vpc uses Global dynamic routing mode and exports custom routes, it pushes peering dynamic routes into all regions of any peered VPC that imports custom routes. Changing eu-isolated-vpc to Regional dynamic routing mode has no effect because the dynamic routing mode of an importing VPC is ignored for peering dynamic routes.eu-isolated-vpc still receives 192.168.44.0/24 in europe-west1 as long as custom route import remains enabled.This configuration would only work if all workloads resided directly inside transit-vpc rather than a peered workload-vpc, and if eu-isolated-vpc disabled custom route import instead of relying on its own dynamic routing mode.
A common misconception is that Global mode on a hub VPC automatically redistributes peered VPC subnets over BGP and that Regional mode on a spoke VPC blocks cross-region peering routes. In practice, explicit Custom advertisement and peering custom route flags are required for both behaviors.
This option correctly enables Global dynamic routing mode on transit-vpc and configures Custom advertisement mode for workload-vpc subnets, but relies on changing eu-isolated-vpc to Regional dynamic routing mode while leaving custom route import enabled.
eu-isolated-vpc: Because transit-vpc is the exporting VPC network and uses Global dynamic routing mode, transit-vpc exports peering dynamic routes (192.168.44.0/24) to all regions of every peered VPC that imports custom routes. The dynamic routing mode of the importing VPC (eu-isolated-vpc) has no effect on peering dynamic route programming, so europe-west1 in eu-isolated-vpc still receives 192.168.44.0/24.eu-isolated-vpc's subnet is not included in transit-vpc's custom advertisements, workloads in europe-west1 will see the imported 192.168.44.0/24 route in their VPC route table and attempt to send packets toward on-premises, violating the isolation requirement.eu-isolated-vpc to Regional mode only affects Cloud Routers owned directly by eu-isolated-vpc, not routes received over VPC Network Peering.--export-custom-routes on transit-vpc and --import-custom-routes on eu-isolated-vpc are both active, dynamic routes propagate into eu-isolated-vpc.This configuration would succeed if eu-isolated-vpc disabled custom route import (or transit-vpc disabled custom route export on that specific peering connection) instead of changing eu-isolated-vpc's dynamic routing mode.
While Regional dynamic routing mode provides traffic isolation for learned routes within a single VPC that owns Cloud Routers, isolating an entire peered spoke VPC from a Global hub requires disabling custom route exchange on that peering link.
This option leaves transit-vpc in Regional dynamic routing mode, adds Custom route advertisements for workload-vpc subnets on transit-vpc Cloud Routers, and introduces a new Cloud Router inside us-central1 of workload-vpc.
us-central1: Because transit-vpc remains in Regional dynamic routing mode, its dynamic route control planes in us-west1 and us-east1 do not share 192.168.44.0/24 with us-central1 and only export peering dynamic routes in us-west1 and us-east1. Consequently, us-central1 in workload-vpc receives no route to 192.168.44.0/24.us-central1 of workload-vpc cannot bridge or re-advertise BGP routes across a VPC peering boundary. Cloud Routers do not establish iBGP sessions with each other across the same or peered VPC networks, and Cloud Router never re-advertises learned dynamic routes.eu-isolated-vpc: Although europe-west1 in eu-isolated-vpc happens not to receive 192.168.44.0/24 while transit-vpc is Regional, us-central1 in workload-vpc fails completely.Keeping transit-vpc in Regional mode would work only if us-central1 had its own Dedicated Interconnect VLAN attachment and Cloud Router directly inside us-central1 of transit-vpc, eliminating the need for cross-region route propagation.
Network engineers sometimes assume deploying an extra Cloud Router in an unserved region enables dynamic route forwarding across VPC peering. However, Google Cloud's Andromeda stack handles packet forwarding using routes programmed by the exporting VPC's dynamic route control plane, not via Cloud Router-to-Cloud Router BGP peering.
This configuration aligns the dynamic routing mode of the exporting hub network (transit-vpc), custom route advertisements on its Cloud Routers, and peering custom route import controls on eu-isolated-vpc. Together, these settings control how Cloud Router discovers, advertises, and propagates Border Gateway Protocol (BGP) routes across regions and peered VPC boundaries.
us-central1: In VPC Network Peering, the dynamic routing mode of the exporting VPC network (transit-vpc) dictates where peering dynamic routes are programmed. Switching transit-vpc to Global dynamic routing mode causes the dynamic route control planes in us-west1 and us-east1 to export only their lowest-MED next hops (west-a and east-a, MED 10) to us-central1, adjusting each MED by an inter-regional cost so us-central1 selects the lowest-cost path while preserving cross-region failover.workload-vpc: Default advertisement mode only announces subnets local to transit-vpc. Switching the transit-vpc Cloud Routers to Custom advertisement mode allows them to announce the workload-vpc subnet CIDR ranges to the on-premises routers.eu-isolated-vpc: Because transit-vpc is in Global mode, it exports dynamic routes in all regions to any peered VPC importing custom routes. Disabling --import-custom-routes on eu-isolated-vpc (or disabling export on that specific peering link) prevents 192.168.44.0/24 from entering europe-west1 while preserving peering subnet routes to transit-vpc.west-b, east-b) during cross-region export and applies inter-regional distance costs.transit-vpc without deploying redundant Cloud Routers in spoke networks.This approach respects Google Cloud's control plane rules: only the exporting VPC's dynamic routing mode governs peering dynamic route scope, custom advertisements are mandatory for peered subnets, and peering import/export flags provide the only valid boundary for isolating eu-isolated-vpc.
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