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 deploys Compute Engine workloads in us-central1 and us-east4 on a Shared VPC connected to an on-premises network via Dedicated Interconnect in Chicago (us-central1) and Ashburn (us-east4), with two VLAN attachments per metro and global dynamic routing enabled. Expanding the Cloud Interconnect entities in Network Topology reveals the following egress traffic flows from us-central1:
vlan-chi-1 and 33% across vlan-chi-2, while Ashburn attachments carry 0%.us-central1 traffic shifts to Ashburn.Which configuration explains this traffic distribution in Network Topology?
BGP MED values influence path preference between routing advertisements, where a lower MED value is strictly preferred over a higher one. Regional dynamic routing restricts a Cloud Router so that it only advertises subnets located within its own Google Cloud region and only programs learned routes for workloads inside that same region.
100 vs. 200). Instead, it treats the lower MED as the sole active path, sending 100% of traffic across vlan-chi-1 and 0% across vlan-chi-2 in an active/passive configuration.us-central1 workloads would not have routes to the Ashburn attachments (us-east4) in their forwarding table and would lose all hybrid connectivity during a Chicago outage.us-central1 subnets to Ashburn's on-premises BGP peers.Network Topology showed 100% of us-central1 traffic on vlan-chi-1 and 0% on vlan-chi-2 during normal operations, and the organization intentionally enforced regional isolation without cross-region failover.
A common misconception is that BGP MEDs act like weighted load-balancing ratios. In Google Cloud, MED is a tie-breaking path preference metric; weighted distribution only occurs when MEDs are equal and the VLAN attachments have different configured capacities.
Equal-Cost Multi-Path (ECMP) routing allows Google Cloud to distribute egress traffic simultaneously across multiple VLAN attachments when Cloud Router receives identical CIDR announcements with equal Border Gateway Protocol (BGP) Multi-Exit Discriminator (MED) values. When paired with global dynamic routing, a Shared VPC propagates routes learned by regional Cloud Routers across all regions while preserving regional locality.
10 Gbps on vlan-chi-1 and 5 Gbps on vlan-chi-2), producing a 2:1 traffic distribution when both sessions advertise identical prefixes and equal MEDs.200 plus the inter-region latency in milliseconds to routes advertised outside the local region, ensuring us-central1 workloads strictly prefer the local Chicago attachments.us-central1 workloads.Unlike options that rely on unequal BGP MEDs (which force active/passive failover rather than load sharing) or regional routing (which prevents cross-region backup), equal-MED capacity-weighted ECMP combined with global dynamic routing accurately accounts for both the 2:1 local distribution and the seamless cross-region failover.
Shared VPC allows a central host project to share a single VPC network and its subnets directly with multiple service projects, enabling all workloads to share hybrid attachments natively. By contrast, VPC Network Peering connects two separate VPC networks privately so their workloads can exchange traffic over internal IP addresses.
The environment actually used a hub-and-spoke multi-VPC topology with VPC Network Peering between separate workload VPCs and a transit VPC, though even then, Network Topology would display separate VPC entities rather than attributing a 2:1 VLAN attachment split to peering.
Integrating Cloud Interconnect into a Shared VPC automatically grants all authorized service projects access to those hybrid links across every region, eliminating per-project peering or duplicate attachments.
5-tuple hash-based ECMP distributes individual network flows across equal-cost paths using source/destination IP, source/destination port, and protocol, while Cloud Router in global dynamic routing mode continuously advertises all VPC subnets across every connected region.
us-central1 subnets out of Ashburn. All subnets are advertised continuously across all regions, with remote advertisements penalized by a higher MED (200 plus inter-region latency in milliseconds).Traffic consisted of only a few large, long-lived elephant flows traversing equal-capacity Cloud VPN tunnels where 5-tuple hashing happened to map two flows to one tunnel and one flow to another.
Understanding the difference between route withdrawal and MED-penalized standby advertisements is essential when analyzing failover behavior in Network Topology.
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