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 connects an on-premises network to a Google Cloud VPC using four dataplaneVersion 2 Dedicated Interconnect VLAN attachments across us-central1 and us-east1, with global dynamic routing and standard best path selection. You must meet these requirements:
us-central1 over us-east1 symmetrically for ingress and egress traffic.10.0.0.0/8 instead of VPC subnets, and drop inbound routes carrying the NO_EXPORT community (65535:65281).Which configuration should you implement?
This configuration reverses the MED priority logic, misuses custom learned routes in place of outbound custom advertisements, attempts to filter custom learned routes with a BGP route policy, and enables BFD echo mode on the peer routers.
us-central1 makes us-east1 the primary active path and demotes us-central1 to passive.--set-custom-learned-route-ranges flag statically injects routes into the VPC as if learned from the peer; it does not advertise 10.0.0.0/8 outbound to on-premises routers, nor does it suppress VPC subnet advertisements.--advertisement-mode=CUSTOM with --advertisement-ranges, not custom learned routes.This option would be correct if lower MED values were applied to us-central1, --advertisement-mode=CUSTOM replaced --set-custom-learned-route-ranges, and BFD echo mode were disabled in favor of control-only mode.
Because BFD echo mode relies on the neighbor router looping UDP echo packets back at the forwarding plane without control-plane involvement, commercial routers often enable it by default. When peering with Cloud Router, administrators must explicitly disable echo mode so both peers use control-only mode.
This option attempts to engineer failover using only Cloud Router's outbound --advertised-route-priority, adds a summary range alongside ALL_SUBNETS, applies a single BGP route policy bidirectionally, and sets BFD to Passive initialization mode on both peers.
--advertised-route-priority values only influences traffic from on-premises toward Google Cloud. Leaving on-premises MED values identical causes Google Cloud's egress traffic to evaluate inter-regional costs or load-balance unpredictably rather than symmetrically preferring us-central1.--advertisement-groups=ALL_SUBNETS instructs Cloud Router to advertise every individual VPC subnet in addition to 10.0.0.0/8, violating the summarization-only requirement.Passive mode on both Cloud Router and the on-premises router leaves neither side responsible for initiating BFD control packets, so the BFD session remains down.--advertisement-mode=CUSTOM, omitting ALL_SUBNETS is required to suppress individual subnet advertisements.Active initialization mode.This option would be correct if lower MEDs were configured on both sides for us-central1, ALL_SUBNETS were omitted, a dedicated inbound BGP route policy were used for 65535:65281, and Cloud Router were set to Active BFD mode.
In a VPC with global dynamic routing, Cloud Router compares MED values across regions after adding inter-regional costs. Relying solely on default on-premises MEDs can cause regional VMs in us-east1 to prefer local us-east1 attachments for egress while return traffic enters via us-central1, breaking symmetry.
This configuration correctly applies symmetric Multi-Exit Discriminator (MED) values to prefer us-central1 over us-east1 and summarizes outbound advertisements to 10.0.0.0/8 using custom advertisement mode. However, it misconfigures both BGP community filtering and Bidirectional Forwarding Detection (BFD) parameters.
NO_EXPORT handling fails: Cloud Router does not automatically recognize or honor well-known BGP communities such as NO_EXPORT or NO_ADVERTISE. Unless you create an explicit inbound BGP route policy matching the literal value 65535:65281, those routes are accepted into the VPC routing table.1000 ms and a minimum multiplier of 5, resulting in a fastest supported detection time of 5000 ms (5 seconds). Specifying 100 ms and a multiplier of 3 is invalid on Cloud Router.1000 ms to 30000 ms, with multipliers from 5 to 16.dataplaneVersion 2 VLAN attachments operate as single-hop neighbors and do not require eBGP multi-hop.This option would be correct if an inbound CEL-based BGP route policy matched literal 65535:65281 to drop those routes, BFD intervals were set to 1000 ms with a multiplier of 5, and eBGP multi-hop were removed or explicitly overridden with BFD single-hop mode.
Network engineers accustomed to on-premises hardware routers often expect sub-second BFD timers like 100 ms x 3. In Google Cloud, BFD runs in asynchronous control-only mode on the control plane, so 5000 ms is the minimum recommended and supported timeout to prevent false-positive session flaps.
This configuration establishes deterministic active/passive failover, strict prefix summarization and community filtering, and rapid Bidirectional Forwarding Detection (BFD) across redundant dataplaneVersion 2 Dedicated Interconnect VLAN attachments.
--advertised-route-priority values on us-central1 Cloud Routers steers on-premises-to-cloud traffic through us-central1. Simultaneously advertising lower MEDs from on-premises routers toward us-central1 ensures Google Cloud's dynamic route control plane selects us-central1 as the primary egress path across the global VPC, avoiding asymmetric routing.--advertisement-mode=CUSTOM with only --advertisement-ranges=10.0.0.0/8 suppresses individual VPC subnet advertisements. Because Cloud Router does not automatically recognize well-known community names, configuring an inbound BGP route policy with a Common Expression Language (CEL) term that matches literal '65535:65281' accurately drops NO_EXPORT-tagged routes before VPC import.--bfd-session-initialization-mode=ACTIVE with 1000 ms transmit/receive intervals and a multiplier of 5 achieves Cloud Router's minimum 5000 ms (5-second) detection timer—far faster than BGP's 60-second hold timer. Removing legacy eBGP multi-hop (or explicitly forcing BFD single-hop mode) ensures compatibility with dataplaneVersion 2 attachments./8 aggregate prefix.Every parameter aligns with Cloud Router's exact protocol constraints: symmetric MED manipulation, custom advertisement isolation, literal community matching in an inbound-only policy, and valid single-hop BFD timers.
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