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 operates a multi-project hub-and-spoke VPC architecture connected through VPC Network Peering. The hub VPC connects to an on-premises network (10.20.0.0/16) over an active/passive Cloud Interconnect topology managed by Cloud Routers.
After a spoke project team provisions a new subnet, workloads in the hub VPC lose connectivity to the on-premises subnet 10.20.4.0/24. Additionally, packet captures reveal asymmetric routing for other on-premises prefixes across the active and passive links. Reviewing Network Analyzer and Cloud Router configurations shows:
Fully shadowed by a peering subnet route for the dynamic route 10.20.4.0/24.Which actions should you take to restore connectivity to 10.20.4.0/24 and eliminate asymmetric routing?
10.20.4.0/24 using equal MED values across both Interconnect BGP sessions with ECMP enabled, and deploy a Network Connectivity Center router appliance to bypass the peering subnet route.Exchanging identical MED values across BGP sessions with equal-cost multipath (ECMP) routing distributes traffic concurrently across links in an active/active model. A Network Connectivity Center (NCC) router appliance enables third-party virtual router VMs inside a VPC to exchange BGP routes with Cloud Router as an NCC spoke.
10.20.4.0/24 would still be routed to the overlapping spoke subnet.10.20.4.0/24, and configure higher MED values on both the Cloud Router side and the on-premises router side for the passive link.Resolving a shadowed dynamic route requires eliminating the IP address overlap with the higher-precedence peering subnet route, while resolving asymmetric routing in an active/passive Cloud Interconnect topology requires matching higher Multi-Exit Discriminator (MED) values on both the Cloud Router and on-premises BGP peers.
10.20.4.0/24: In Google Cloud route selection order, local and peering subnet routes always take the highest precedence over dynamic routes. Because the spoke VPC's subnet overlaps 10.20.4.0/24, packets destined for the on-premises range are misdirected to the peering spoke. Replacing or modifying the spoke subnet so its CIDR range is completely disjoint from 10.20.4.0/24 removes the shadowing peering subnet route and allows the Cloud Router dynamic route to become active again.Fully shadowed by a peering subnet route) rather than masking symptoms.No BGP attribute tuning, firewall adjustment, or static route can override an overlapping peering subnet route. Combining disjoint subnet addressing with bidirectional MED alignment resolves both the Layer 3 shadowing failure and the active/passive path asymmetry using Google Cloud networking best practices.
med.set to advertise a lower MED for 10.20.4.0/24 on the active session, and run gcloud compute routers get-status to promote the dynamic route above the peering subnet route.get-status doCloud Router BGP route policies use expressions such as med.set to modify Border Gateway Protocol (BGP) attributes on advertised or learned dynamic routes, while gcloud compute routers get-status is a read-only diagnostic command that reports bestRoutesForRouter and bestRoutes per VPC and region.
gcloud compute routers get-status inspects the active routing table and best dynamic paths; it cannot alter route priorities or promote a dynamic route above a subnet route.routers.getRouterStatus / gcloud compute routers get-status provides visibility into routeStatus and nextHopVpnTunnel or VLAN attachment paths without mutating state.bestRoutesForRouter.10.20.4.0/24 on the active Cloud Router with a higher priority, and enable graceful restart on both the Cloud Router and on-premises BGP sessions.Custom learned routes allow administrators to manually define prefixes on a Cloud Router BGP session so they are programmed into the VPC routing table as dynamic routes. Graceful restart is a BGP resilience feature that preserves forwarding state and prevents traffic disruption when a Cloud Router or on-premises BGP router undergoes a task or control-plane restart.
10.20.4.0/24 remains completely ineffective while the overlapping spoke subnet exists.10.20.4.0/24 over BGP (with no overlapping VPC subnet present) and you also needed to prevent brief traffic blackouts during Cloud Router software task restarts.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