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 has a Google Cloud VPC network configured with global dynamic routing and standard BGP best path selection (STANDARD). Two Dedicated Interconnect links connect the VPC to separate on-premises data centers:
us-west1 (Primary): Peers with ASN 65101, advertising 10.50.0.0/16 with MED 100.us-east1 (Backup): Peers with ASN 65102, advertising 10.50.0.0/16 with MED 500.Both paths have identical AS-path lengths and IGP origins. Currently, us-east1 VMs still route traffic via us-east1, and return traffic arrives asymmetrically. You need all regions to prefer us-west1 when healthy without distance penalties, and ensure symmetric return routing.
Which configuration should you implement?
Regional dynamic routing mode (REGIONAL) restricts dynamic routes learned by a Cloud Router to the specific Google Cloud region where that Cloud Router resides, preventing cross-region advertisement of on-premises prefixes. AS-path prepending artificially lengthens the AS_PATH attribute by repeating an ASN multiple times so that BGP speakers—including Cloud Router in STANDARD mode—treat that path as less preferred.
GLOBAL to REGIONAL dynamic routing mode stops Cloud Routers in us-west1 from propagating 10.50.0.0/16 routes to us-east1. Consequently, VMs in us-east1 cannot route through us-west1 at all and remain locked onto the us-east1 backup link.bgpInterRegionCost to ADD-COST-TO-MED (which only takes effect in GLOBAL mode) adds inter-regional latency costs to remote-region MED values, violating the requirement to compare paths without distance penalties.us-east1 would make us-west1 win Step 1 (shortest AS-path length) if GLOBAL routing were active, this option fails to configure --advertised-route-priority on Cloud Router or Local Preference and community policies on-premises, leaving return traffic asymmetric.REGIONAL mode, Cloud Routers neither export learned routes to other regions nor advertise subnets from remote regions to on-premises peers.STANDARD mode: Cloud Router evaluates shortest AS-path length (Step 1) and origin type (Step 2) before considering neighbor ASN and MED (Step 4).Using REGIONAL dynamic routing mode and AS-path prepending would be appropriate if each VPC region were required to stay strictly isolated to its own local Interconnect link without cross-region transit or centralized active/passive failover.
Local Preference is a well-known discretionary BGP attribute exchanged exclusively within an Internal BGP (iBGP) Autonomous System to indicate the preferred exit point for outbound traffic. BGP community strings are optional transitive attributes used to tag routes with metadata so downstream routers can automate policy decisions such as adjusting Local Preference, filtering prefixes, or triggering AS-path prepending.
--advertised-route-priority), AS-path length, origin type, and VPC-level routingConfig settings.bgpAlwaysCompareMed set to False causes Cloud Router to group learned routes by neighbor ASN (65101 and 65102) and compare MED only within each group. As a result, both us-west1 (MED 100) and us-east1 (MED 500) keep top rank within their respective ASNs, and us-east1 discards the us-west1 route during the smallest inter-regional cost tie-breaker.--advertised-route-priority (MED) on the us-east1 Cloud Router and enforcing matching policies on the on-premises routers, return traffic remains uncoordinated.STANDARD mode), and custom learned route priorities, but not iBGP Local Preference or BGP community policy automation.bgpAlwaysCompareMed is False, next hops from different ASNs remain tied until Cloud Router removes routes with nonzero inter-regional costs.This approach would be correct if bgpAlwaysCompareMed were set to True with bgpInterRegionCost set to DEFAULT, --advertised-route-priority were increased on us-east1, and Local Preference and community strings were configured on the on-premises BGP routers rather than on Cloud Router.
In Google Cloud VPC networks using standard BGP best path selection (STANDARD), Multi-Exit Discriminator (MED) comparison across different neighbor Autonomous System Numbers (ASNs) is governed by bgpAlwaysCompareMed, while cross-region distance weighting is controlled by bgpInterRegionCost. To engineer symmetric active/passive forwarding across hybrid links, Cloud Router outbound advertisements use --advertised-route-priority (base MED), while on-premises enterprise routers use Local Preference and BGP community strings to automate inbound path selection.
STANDARD mode, bgpAlwaysCompareMed is False, so Cloud Router groups next hops by neighbor ASN (65101 and 65102) and selects the lowest MED within each ASN group. Because each ASN only advertises one path, both us-west1 (MED 100) and us-east1 (MED 500) survive into the global tie-breaking phase, where us-east1 drops the remote us-west1 route due to 0 inter-regional cost. Setting bgpAlwaysCompareMed to True removes ASN grouping so MED 100 beats MED 500 directly.bgpInterRegionCost to DEFAULT ensures Cloud Router evaluates original MED values without adding inter-regional costs, guaranteeing us-west1 wins from us-east1 and every other region.--advertised-route-priority (MED) on the us-east1 Cloud Router BGP sessions signals to on-premises peers that us-east1 is the backup path. Applying on-premises route policies—such as matching BGP community strings to assign a higher Local Preference on us-west1 routes—ensures on-premises core routers also forward return traffic via us-west1 even across separate ASNs.us-west1 during normal operations and automatically fail over to us-east1 if the primary path goes down.STANDARD mode evaluates AS-path length and origin type consistently across all Cloud Routers in the VPC.This configuration is optimal because it addresses both directions of hybrid traffic using the native capabilities of each routing domain: VPC-level routingConfig attributes (bgpAlwaysCompareMed and bgpInterRegionCost) and Cloud Router MED for GCP-to-on-premises traffic, paired with Local Preference and community-based policies on the on-premises routers for return traffic.
Legacy best path selection mode (LEGACY) is Cloud Router's older route-ranking algorithm, where AS-path length is only evaluated within individual Cloud Router BGP tasks and MED values are compared globally with automatic inter-regional distance costs added. Conversely, bgpInterRegionCost (ADD-COST-TO-MED or DEFAULT) is an advanced standard mode (STANDARD) parameter that controls whether inter-regional latency costs are added to received MED values.
bgpInterRegionCost field is only valid when bgpBestPathSelectionMode is set to STANDARD. Attempting to specify bgpInterRegionCost while using LEGACY mode is unsupported and must be omitted in LEGACY configurations.ADD-COST-TO-MED (or LEGACY mode's implicit inter-regional cost addition) adds distance penalties to routes received from remote regions. If the inter-regional cost between us-west1 and us-east1 plus 100 exceeds 500, us-east1 VMs will continue preferring the local us-east1 backup path.--advertised-route-priority on us-east1 instructs on-premises routers to prefer us-east1 over us-west1 for traffic entering GCP, which reinforces asymmetric routing rather than fixing it.bgpAlwaysCompareMed and bgpInterRegionCost must be omitted when bgpBestPathSelectionMode is LEGACY.LEGACY mode does not evaluate AS-path length consistently across different Cloud Router software tasks in the VPC.100) indicate higher priority than larger numerical MED values (500).--advertised-route-priority without aligning on-premises Local Preference or MED comparison policies across ASNs fails to guarantee symmetric return paths.This general direction would only apply if the goal were to make us-east1 the primary path instead of us-west1, and if STANDARD mode were retained with ADD-COST-TO-MED intentionally used to favor regional egress over remote egress.
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