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.
You manage an active/passive Dedicated Interconnect deployment using Dataplane version 2 VLAN attachments. Your Cloud Router BGP peer uses default BFD settings (1000 ms intervals, multiplier 5), while your on-premises router uses 250 ms intervals and multiplier 3 for attempted sub-second detection.
Transient jitter causes 3.5-second packet-loss bursts, triggering premature on-premises BFD drops and BGP route flapping. You must update both sides to:
Which configuration should you apply?
--bfd-min-transmit-interval=2000, --bfd-min-receive-interval=2000, and --bfd-multiplier=4, and configure the on-premises router with 2000 ms intervals and a detection multiplier of 4.Increasing BFD transmit and receive intervals to 2000 ms halves the BFD control packet rate compared to 1000 ms, reducing control-plane processing overhead. Pairing 2000 ms intervals with a multiplier of 4 mathematically equals 8000 ms (2000 ms * 4), which many traditional enterprise routers permit.
--bfd-multiplier to be set between 5 packets and 16 packets (default 5). Specifying --bfd-multiplier=4 via the Google Cloud CLI or console is rejected as out of range.2000 ms intervals does not maintain the fastest valid probe cadence supported by Cloud Router (1000 ms), even if paired with a valid multiplier.5 to guard against premature false-positive transitions over cloud-edge control planes.2000 ms interval and the lowest valid multiplier (5), the fastest achievable detection time would be 10000 ms (10 seconds), missing the 8000 ms target.1000 ms intervals.Both BGP peers supported a multiplier of 4 (not applicable to Cloud Router) and your primary objective was reducing BFD control-plane packet overhead rather than maintaining a 1000 ms probe cadence.
--bfd-min-transmit-interval=1000, --bfd-min-receive-interval=1000, and --bfd-multiplier=8, and leave the on-premises router at 250 ms intervals with a detection multiplier of 3.This configuration updates Cloud Router's detection multiplier to 8 while relying on RFC 5880 timer negotiation to raise the on-premises router's 250 ms intervals to 1000 ms. While RFC 5880 negotiates transmit and receive intervals (max(250 ms, 1000 ms) = 1000 ms), the detection multiplier is strictly local to each router and is never negotiated or synchronized across the session.
3, its receive detection time remains 1000 ms * 3 = 3000 ms (3 seconds). A 3.5-second packet-loss burst still misses 3 consecutive packets, causing the on-premises router to tear down BFD and flap BGP routes.8000 ms requirement.Detection time = Agreed transmit interval * Local BFD multiplier independently.You also updated the on-premises router's detection multiplier from 3 to 8 alongside the Cloud Router change, since 250 ms intervals negotiate up to 1000 ms automatically under RFC 5880.
--bfd-min-transmit-interval=500, --bfd-min-receive-interval=500, and --bfd-multiplier=16, and configure the on-premises router with 500 ms intervals and a detection multiplier of 16.Sub-second BFD intervals (500 ms) combined with the maximum multiplier (16) attempt to achieve an 8000 ms detection window (500 ms * 16) by sending control packets twice per second. On dedicated hardware routers across local optical links, higher-frequency probes paired with larger multipliers are often used to absorb brief microbursts.
Cloud Router does not support sub-second BFD intervals. Both --bfd-min-transmit-interval and --bfd-min-receive-interval strictly require values between 1000 ms and 30000 ms. Running gcloud compute routers update-bgp-peer or editing the peer in the Google Cloud console with 500 ms results in an immediate parameter validation error.
1000 ms for both transmit and receive timers.250 ms or 500 ms), RFC 5880 automatically negotiates the agreed interval up to Cloud Router's 1000 ms minimum—meaning sub-second probing never occurs on the wire.16 is valid on Cloud Router (5–16 packets), but when paired with the lowest valid interval (1000 ms), it yields a 16-second detection time rather than 8 seconds.The BGP session terminated between two third-party hardware routers (without Cloud Router in the path) that natively support 500 ms BFD timers and required an 8000 ms detection window at a 500 ms probe rate.
--bfd-min-transmit-interval=1000, --bfd-min-receive-interval=1000, and --bfd-multiplier=8, and configure the on-premises router with 1000 ms intervals and a detection multiplier of 8.Bidirectional Forwarding Detection (BFD) on Cloud Router monitors forwarding-path liveness independently of slower BGP keepalive and hold timers. Using the Google Cloud CLI (gcloud compute routers update-bgp-peer) or Google Cloud console, administrators configure three core parameters: minimum transmit interval (--bfd-min-transmit-interval), minimum receive interval (--bfd-min-receive-interval), and detection multiplier (--bfd-multiplier). Under RFC 5880, each direction's agreed transmit interval is negotiated as the higher value between the sender's minimum transmit interval and the receiver's minimum receive interval.
1000 ms transmit and receive intervals, establishing an agreed transmit interval of 1000 ms in each direction. With a matching detection multiplier of 8 on both Cloud Router and the on-premises router, Detection time = 1000 ms * 8 = 8000 ms symmetrically.1000 ms to 30000 ms and multipliers from 5 to 16 packets. Using 1000 ms maintains the highest probe frequency allowed by Cloud Router.1000–30000 ms intervals and 5–16 multiplier).20 s / 60 s BGP keepalive and hold timers.This configuration balances rapid failure detection against transient network jitter within Cloud Router's supported boundaries. Unlike sub-second attempts that fail validation, asymmetric multipliers that leave the peer vulnerable at 3 seconds, or 2000 ms intervals that either violate multiplier limits or slow detection to 10 seconds, pairing 1000 ms intervals with a symmetric multiplier of 8 satisfies every operational constraint.
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