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 VPC network (10.10.0.0/16) in us-central1 uses an active/passive hybrid connection through a stateful on-premises firewall:
bgp-interconnect): Dedicated Interconnect (Peer ASN 65100) learns 172.16.0.0/16 (MED 100) and advertises 10.10.0.0/16 using custom advertisement mode (--advertised-route-priority=100).bgp-vpn): HA VPN (Peer ASN 65100) learns 172.16.0.0/17 (MED 500), advertises 10.10.0.0/16 (--advertised-route-priority=500), and has a custom learned route for 172.16.200.0/24 (--custom-learned-route-priority=500).Traffic between VPC VMs and 172.16.200.0/24 is dropped by the firewall due to asymmetric routing. What should you do on Cloud Router to restore symmetric active/passive forwarding?
bgp-vpn BGP session to set --custom-learned-route-priority to 65535 for 172.16.200.0/24 so the bgp-interconnect route for 172.16.0.0/16 takes precedence.--custom-learned-route-priority doesThe --custom-learned-route-priority flag sets the MED value (from 0 to 65535) applied to all custom learned routes on a specific BGP session. Lower numerical values represent higher preference, while 65535 represents the least preferred MED value.
172.16.200.0/24 is more specific than 172.16.0.0/16, Google Cloud discards the 172.16.0.0/16 route on bgp-interconnect before MED values are ever inspected.65535 on bgp-vpn, egress packets to 172.16.200.0/24 will continue to select the /24 custom learned route over the HA VPN tunnel while return packets still arrive over Dedicated Interconnect./24 route with MED 65535 always beats a /16 route with MED 0 or 100./24 route breaks failover: Removing the custom learned route from bgp-vpn without advertising 172.16.200.0/24 over VPN would leave 172.16.200.0/24 unreachable during an Interconnect outage, because bgp-vpn only learns 172.16.0.0/17.Both bgp-interconnect and bgp-vpn already had routes for the exact same 172.16.200.0/24 prefix, and bgp-vpn was mistakenly winning because its custom learned route priority was lower than bgp-interconnect's MED.
global and enable routingConfig.bgpAlwaysCompareMed so Cloud Router compares the MED 100 route on bgp-interconnect against the MED 500 route on bgp-vpn.bgpAlwaysCompareMed doGlobal dynamic routing mode propagates dynamic routes learned by Cloud Routers in one region to subnets in all other Google Cloud regions of the VPC. routingConfig.bgpAlwaysCompareMed (available in standard best path selection mode) instructs Cloud Router to compare MED values across candidate routes for the same prefix even when those routes were learned from different neighbor ASNs.
bgpAlwaysCompareMed only modifies how MEDs are compared among candidate next hops for an identical destination prefix. It cannot cause a 172.16.0.0/16 route (MED 100) to beat a more specific 172.16.200.0/24 route (MED 500).bgp-interconnect and bgp-vpn peer with ASN 65100, meaning MED comparison across these sessions is not blocked by differing neighbor ASNs.us-central1, so switching from regional to global dynamic routing mode provides no routing benefit for this conflict.IGP > EGP > Incomplete), and neighbor ASN/MED strictly on a per-unique-prefix basis.IGP origin is preferred over a custom learned route (which always has an Incomplete origin) before MED is evaluated.Both bgp-interconnect and bgp-vpn learned the same prefix from different neighbor ASNs (such as 65100 and 65200) with identical AS path lengths and origin types, and Cloud Router was failing to prefer the lower MED across the two ASNs.
172.16.200.0/24 as a custom learned route on the bgp-interconnect BGP session with --custom-learned-route-priority=100.Custom learned routes allow Cloud Router to treat manually specified IP prefixes as if they were learned dynamically from a BGP peer, assigning each session's configured --custom-learned-route-priority as its MED value. Adding 172.16.200.0/24 to bgp-interconnect with priority 100 creates an explicit /24 candidate dynamic route on the primary Dedicated Interconnect session alongside the existing /24 custom learned route (priority 500) on bgp-vpn.
bgp-vpn held the only /24 route for 172.16.200.0/24, causing Google Cloud's longest-prefix match rule to pick bgp-vpn over bgp-interconnect's broader 172.16.0.0/16 route before ever comparing MED values.172.16.200.0/24 configured as a custom learned route on both sessions, both candidate routes share the exact same prefix length (/24), AS path length (1), neighbor ASN (65100), origin (Incomplete), and inter-region cost (0). Cloud Router then selects bgp-interconnect because its MED (100) is smaller than bgp-vpn's MED (500).172.16.200.0/24 now uses Dedicated Interconnect, matching the ingress return path selected by the on-premises router (--advertised-route-priority=100 on bgp-interconnect).bgp-interconnect goes down, its /24 custom learned route is automatically withdrawn and traffic fails over to bgp-vpn (MED 500)./24 prefix specificity across redundant hybrid links so MED values govern active/passive selection.172.16.0.0/16 and 172.16.0.0/17 BGP routing behavior intact.Unlike adjusting advertised priorities, raising the backup MED, or changing global routing flags, adding the matching /24 custom learned route with a lower MED directly addresses the longest-prefix match precedence rule while maintaining resilient failover to HA VPN.
bgp-vpn BGP session to increase --advertised-route-priority to 1000 and keep custom advertisement mode enabled for 10.10.0.0/16.--advertised-route-priority and custom advertisement mode doOn Cloud Router, --advertised-route-priority sets the base Multi-Exit Discriminator (MED) value that Cloud Router sends to an external BGP peer for outbound route advertisements. When combined with custom advertisement mode (--advertisement-mode=custom), it controls which Google Cloud prefixes are announced to the on-premises router and how the on-premises network ranks ingress paths into the VPC.
--advertised-route-priority only affects how on-premises routers select a path toward Google Cloud (10.10.0.0/16). It has zero effect on how the VPC selects a next hop for traffic traveling toward 172.16.200.0/24.bgp-interconnect already advertises 10.10.0.0/16 with MED 100 and bgp-vpn advertises it with MED 500, on-premises routers already prefer Dedicated Interconnect. Increasing the VPN advertised MED from 500 to 1000 leaves the ingress path unchanged while leaving egress stuck on bgp-vpn.Traffic from the VPC was already exiting over bgp-interconnect, while return traffic from on-premises to 10.10.0.0/16 was mistakenly arriving over bgp-vpn because bgp-vpn had a lower --advertised-route-priority than bgp-interconnect.
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