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 runs an active/active Dedicated Interconnect setup in us-central1 with two Dataplane v2 VLAN attachments and Bidirectional Forwarding Detection (BFD). After replacing one on-premises Cisco router, you observe:
Established using the allocated /29 link-local subnet, and the second link is healthy.ebgp-multihop 4 configured, causing BFD to inherit multi-hop mode.You must fail over traffic without packet loss, remediate the issue, and validate restoration. Which sequence of actions should you take?
ebgp-multihop 4 on the on-premises router, update the Cloud Router BGP peer to enable BFD multi-hop and BFD authentication, and verify recovery using the bfd/session_up Cloud Monitoring metric and ping tests to the Cloud Router interface.This approach tries to align Cloud Router with the on-premises router's inherited BFD multi-hop behavior and add BFD authentication rather than eliminating the multi-hop dependency on a Dataplane v2 attachment.
ebgp-multihop, Dataplane v2 attachments do not require multi-hop eBGP peering.bfd/session_up metric in Cloud Monitoring is a valid control-plane check, it must be paired with end-to-end VM testing.Cloud Router supported BFD multi-hop and authentication, and end-to-end testing targeted a Compute Engine VM instead of the Cloud Router link-local interface.
200 ms with a multiplier of 3 for sub-second detection, re-enable BGP, and verify restoration using gcloud compute interconnects get-diagnostics.This option properly drains traffic via BGP, but attempts to force sub-second BFD timers (200 ms transmit/receive and multiplier 3) and uses Layer 1 optical diagnostics to validate Layer 3 recovery.
transmit and receive interval of 1000 ms and a minimum detection multiplier of 5, resulting in a minimum detection timeout of 5000 ms (5 seconds).ebgp-multihop 4 inheritance issue, so BFD still fails to establish in single-hop mode.gcloud compute interconnects get-diagnostics reports physical-layer metrics such as receivingOpticalPower and transmittingOpticalPower for Dedicated Interconnect circuits; it does not verify BFD session state, BGP route programming, or end-to-end VPC connectivity.1000 ms is overridden by Cloud Router and risks session flaps if timeouts fall below 5000 ms.You were resolving a Layer 1 optical signal degradation issue rather than a BFD multi-hop misconfiguration, and validating physical transceiver power levels.
--no-admin-enabled to fail over traffic, change the on-premises subinterface mask from /29 to /30, re-enable the attachment, and validate end-to-end recovery by pinging the Cloud Router link-local IP address.Using --no-admin-enabled immediately administratively shuts down the entire VLAN attachment at the data plane layer rather than gracefully withdrawing BGP routes, while changing the link-local interface mask from /29 to /30 alters the Layer 3 peering subnet.
/29 CIDR from 169.254.0.0/16 for every VLAN attachment; reconfiguring the on-premises subinterface to /30 is a common misconfiguration that creates a subnet mismatch.169.254.x.x) produces unpredictable results and does not verify end-to-end data plane reachability into the VPC.ebgp-multihop 4 intact does not resolve the BFD multi-hop inheritance failure.--no-admin-enabled) stops forwarding within one to two minutes and should only be used when zero packets must cross the link./29 range are assigned to the Cloud Router and on-premises subinterface, while the remaining addresses are reserved by Google Cloud.Zero-packet-leakage isolation were required regardless of transient drops, the /29 mask were preserved, ebgp-multihop were removed, and validation targeted a VPC VM.
ebgp-multihop 4 or configure fall-over bfd single-hop on the on-premises router, re-enable BGP, and verify the bfd/session_up metric alongside end-to-end tests to a VPC Compute Engine VM.Disabling only the BGP session gracefully drains traffic onto the healthy redundant attachment, while removing ebgp-multihop 4 or explicitly setting neighbor x.y.y.z fall-over bfd single-hop aligns the on-premises router with Cloud Router's BFD single-hop requirement.
ebgp-multihop 4 (or enforcing fall-over bfd single-hop on Cisco IOS/IOS-XE) ensures BFD negotiates in single-hop mode and restores 5-second failure detection.bfd/session_up Cloud Monitoring metric (along with Cloud Router status and Cloud Logging) confirms the BFD session is up, and testing from on-premises to a VPC Compute Engine VM validates true end-to-end data plane forwarding./29 link-local addressing and active/active ECMP forwarding architecture.It directly resolves the root cause of BFD negotiation failure on Dataplane v2 attachments while following Google Cloud's recommended graceful traffic-drain and end-to-end verification procedures.
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