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 VPC network configured with global dynamic routing mode and the default legacy best path selection mode. Dedicated Interconnect VLAN attachments connect us-east1 (cr-east) and us-west1 (cr-west) to your on-premises network, with VPC subnets deployed in both regions.
You must configure BGP traffic engineering to meet these requirements:
us-east1 as primary and us-west1 as standby, avoiding asymmetric routing.us-west1 on-premises router so Google Cloud prefers us-east1 for egress across all Cloud Routers.172.16.0.0/16 from a peered VPC network.Which configuration should you implement?
--advertisement-mode=CUSTOM, --set-advertisement-groups=ALL_SUBNETS, and --set-advertisement-ranges=172.16.0.0/16 on both Cloud Routers, set a higher --advertised-route-priority on cr-west BGP sessions than on cr-east, and configure AS path prepending on the us-west1 on-premises router.This solution combines standard best path selection mode, Cloud Router custom route advertisements with ALL_SUBNETS, and bidirectional BGP metric engineering using MED (--advertised-route-priority) and AS path prepending to create deterministic, symmetric active/passive hybrid routing across regions.
us-west1 with a prepended AS path are consistently less preferred than shorter-path routes learned via cr-east, even for VMs inside us-west1.--advertised-route-priority (base MED) on cr-west's BGP sessions than on cr-east's sessions (accounting for global dynamic routing inter-regional costs) ensures on-premises routers prefer us-east1 for inbound traffic to Google Cloud, matching the outbound path and preventing asymmetric routing.--advertisement-mode=CUSTOM with --set-advertisement-groups=ALL_SUBNETS preserves automatic advertisement of all regional and remote-region VPC subnets under global dynamic routing mode, while --set-advertisement-ranges=172.16.0.0/16 announces the peered VPC CIDR that DEFAULT mode excludes.Always compare or Conditionally compare) across all Cloud Routers.us-east1 interconnect fails, BGP withdraws the primary routes and traffic fails over cleanly in both directions to us-west1.Only this option satisfies all three requirements simultaneously: standard mode makes cross-region AS path prepending effective, ALL_SUBNETS plus custom ranges advertises both VPC and peered CIDRs, and a higher MED on cr-west aligns ingress path selection with egress path selection.
--advertisement-mode=CUSTOM and --set-advertisement-ranges=172.16.0.0/16 on both Cloud Routers without setting advertisement groups, set a higher --advertised-route-priority on cr-west BGP sessions than on cr-east, and configure AS path prepending on the us-west1 on-premises router.Enabling --advertisement-mode=CUSTOM on a Cloud Router switches it from automatic VPC subnet discovery to explicit prefix announcement. By specifying only --set-advertisement-ranges=172.16.0.0/16 without including --set-advertisement-groups=ALL_SUBNETS, you instruct Cloud Router to advertise exclusively the custom IP range list.
ALL_SUBNETS, neither cr-east nor cr-west advertises the local VPC subnets in us-east1 and us-west1 to the on-premises routers.172.16.0.0/16 (the peered VPC range) and will lose dynamic reachability to workloads residing inside the primary VPC's subnets.ALL_SUBNETS prevents Cloud Router from dynamically tracking and announcing existing or newly created VPC subnets across both regions.DEFAULT advertisement mode, Cloud Router advertises VPC subnets according to the network's regional or global dynamic routing mode, while excluding static routes and peered VPC ranges.CUSTOM mode, VPC subnets are omitted unless --set-advertisement-groups=ALL_SUBNETS (or all_subnets) is configured alongside custom ranges.ALL_SUBNETS must also be preserved if session-level customization is used.This option would be valid only if the organization intentionally wanted to hide all primary VPC subnets from the on-premises network and expose solely the 172.16.0.0/16 CIDR block—or if --set-advertisement-groups=ALL_SUBNETS were added to the Cloud Router configuration.
--advertisement-mode=CUSTOM, --set-advertisement-groups=ALL_SUBNETS, and --set-advertisement-ranges=172.16.0.0/16 on both Cloud Routers, set a lower --advertised-route-priority on cr-west BGP sessions than on cr-east, and configure AS path prepending on the us-west1 on-premises router.The --advertised-route-priority flag defines the base Multi-Exit Discriminator (MED) value that Cloud Router attaches to routes it advertises to on-premises BGP peers. In BGP route selection, lower MED values have higher preference than higher MED values.
--advertised-route-priority on cr-west makes the us-west1 path more attractive to on-premises routers for traffic entering Google Cloud (ingress). Meanwhile, AS path prepending on the us-west1 on-premises router makes us-east1 more attractive to Google Cloud for traffic leaving the VPC (egress).us-west1 while return egress traffic exits through us-east1. Stateful firewalls or security appliances at the hybrid perimeter will drop return packets due to missing session state, directly violating the requirement to avoid asymmetric routing.us-east1 acting as the active path in both directions, us-west1 becomes the active ingress path while us-east1 acts as the active egress path.0) are preferred over higher numerical MED values (up to 65535).This configuration would be correct if us-west1 were intended to be the primary path and AS path prepending were applied to the us-east1 on-premises router—or if --advertised-route-priority on cr-west were set higher than on cr-east.
--advertisement-mode=CUSTOM, --set-advertisement-groups=ALL_SUBNETS, and --set-advertisement-ranges=172.16.0.0/16 on both Cloud Routers, set a higher --advertised-route-priority on cr-west BGP sessions than on cr-east, and configure AS path prepending on the us-west1 on-premises router.Legacy best path selection mode is the default routing evaluation model for newly created Google Cloud VPC networks. In this mode, each Cloud Router BGP task independently evaluates AS path length, origin type, and Multi-Exit Discriminator (MED) values only for prefixes received across the BGP sessions managed by that specific software task.
cr-east in us-east1 and cr-west in us-west1 run separate BGP tasks across different regions, AS path prepending applied on the us-west1 on-premises router will not cause us-east1 to be preferred globally.us-west1 will egress through cr-west despite the longer AS path, violating the active/passive requirement.CUSTOM mode with ALL_SUBNETS and 172.16.0.0/16 correctly advertises both VPC and peered prefixes, but does not fix the egress path selection flaw.This configuration would work only if you abandoned AS path prepending for egress engineering and instead configured the us-west1 on-premises router to advertise a higher MED value than us-east1—or if the VPC network were switched to standard best path selection mode.
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