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. BFD (1000 ms intervals, multiplier 5) and BGP Graceful Restart (60 s hold timer, 300 s stalepath timer) are enabled on both Cloud Router and the on-premises router.
During a simulated data-plane outage on the primary path, traffic is blackholed for several minutes instead of failing over in 5 seconds. You observe:
bfd/session_up drops to 0 and bfd/session_flap_events_count records event_type="ControlDetectionTimeExpired".CONFIG_DISABLED for the BGP peer.show bfd neighbors on the peer displays C bit: 0.What is the root cause of the delayed failover, and how should you resolve it?
C) bit to 0, the on-premises router interprets the ControlDetectionTimeExpired BFD failure as a possible control-plane restart and enters BGP Graceful Restart instead of immediately failing over. Configure the on-premises router so that a BFD timeout triggers an immediate BGP teardown and failover even when Graceful Restart is enabled.In RFC 5880, the Control Plane Independent (C) bit in BFD control packets indicates whether the BFD implementation operates independently of the router's control plane. Cloud Router sets the C bit to 0 because its BFD process is control-plane dependent. When BGP Graceful Restart is enabled alongside BFD, a BFD detection timeout from a peer advertising C bit: 0 creates ambiguity: the receiving router cannot determine whether the outage was caused by a control-plane restart or a data-plane forwarding failure.
Each diagnostic signal in the scenario points directly to this interoperability behavior:
bfd/session_up = 0 and event_type="ControlDetectionTimeExpired": Confirms Cloud Router missed five consecutive BFD control packets (1000 ms * 5 = 5000 ms) due to the data-plane outage rather than sending an intentional AdminDown message.CONFIG_DISABLED in Cloud Logging: Confirms that Cloud Router properly reacted to the expired BFD control detection timer by immediately stopping its local BGP session.C bit: 0 in show bfd neighbors: Explains why the on-premises router preserved stale routes and entered BGP Graceful Restart (waiting up to the 300 s stalepath timer) rather than withdrawing routes and failing over to the backup link in 5 seconds.C bit: 0) to immediately tear down the BGP session and trigger traffic failover instead of invoking Graceful Restart.AdminDown) continue to preserve data-plane traffic.Adjusting the on-premises router's BFD-to-Graceful-Restart policy resolves the blackholing during link faults while retaining 5-second BFD failover and non-disruptive Cloud Router software maintenance.
4 was exceeded, delaying route withdrawal. Reduce the BFD multiplier on Cloud Router from 5 to 2 to force faster teardown.BFD dampening is an internal Cloud Router protection mechanism that prevents rapid, repeated BFD session flaps from destabilizing BGP. It uses a fixed penalty system that cannot be tuned by administrators. The BFD multiplier defines how many consecutive missed BFD control packets trigger a session-down declaration (Detection time = Agreed transmit interval * BFD multiplier).
This option misinterprets both the dampening state and Cloud Router's supported BFD parameters:
0 to 1, which is well below the suppression threshold of 4.CONFIG_DISABLED log entry confirms that Cloud Router's BFD process did notify BGP and stopped the BGP session when the detection timer expired. The multi-minute delay occurs on the on-premises router holding stale routes in Graceful Restart.2.0, increases to 1 on the first flap, and doubles on each subsequent flap (2, 4, 8); suppression only begins when the penalty exceeds 4.5 and 16 packets (default 5), ensuring at least a 5-second detection time at minimum intervals.BFD dampening would be the cause if an unstable link suffered four or more consecutive BFD flaps in a short window (pushing the penalty to 8), suppressing further BFD-down notifications to Cloud Router's BGP process.
AdminDown message, causing the on-premises router to keep stale paths during the BGP hold timer. Increase the on-premises BGP hold timer above 120 seconds and disable BFD on the primary attachment.When both BFD and BGP Graceful Restart are enabled, Cloud Router handles planned software maintenance by sending a BFD AdminDown message to the on-premises peer before restarting its router task. Upon receiving AdminDown, the peer keeps the BGP session state preserved and enters Graceful Restart mode so data-plane forwarding continues uninterrupted. A BGP hold timer of at least 60 seconds ensures the session survives brief control-plane task migrations.
The observed telemetry directly contradicts a planned maintenance event:
event_type="ControlDetectionTimeExpired", not AdminDown. This proves BFD control packets stopped arriving across the forwarding path.CONFIG_DISABLED is logged when the BFD control detection timer expires on a BFD-enabled session, whereas planned maintenance logs Maintenance of router task: BGP sessions will restart.bfd/session_flap_events_count distinguishes between "AdminDown" and "ControlDetectionTimeExpired" via the event_type label.This explanation would apply if Cloud Logging showed Maintenance of router task: BGP sessions will restart., bfd/session_flap_events_count recorded AdminDown, and traffic dropped because the on-premises hold timer was too short (under 60 seconds) or Graceful Restart was disabled.
ebgp-multihop 4 on the on-premises router and lower Cloud Router's minimum transmit interval to 300 ms.Cloud Router operates BFD strictly in asynchronous, control-only, single-hop mode (RFC 5880 and RFC 5881). It does not support BFD multi-hop, demand mode, echo mode, or BFD authentication. Under RFC 5880, the agreed transmit interval in each direction is negotiated to the slower (higher) value between the sender's minimum transmit interval and the receiver's minimum receive interval.
This diagnosis conflicts with both the observed behavior and Cloud Router configuration limits:
bfd/session_up dropped from 1 to 0 with ControlDetectionTimeExpired, the single-hop BFD session was already active and timing out after 5 seconds—not failing to establish due to multi-hop mode.ebgp-multihop breaks BFD: Dataplane version 2 VLAN attachments do not require ebgp-multihop. Adding ebgp-multihop 4 can cause on-premises routers to inherit BFD multi-hop mode, which breaks BFD interoperability unless fall-over bfd single-hop is explicitly configured.300 ms transmit interval.1000 ms and 30000 ms (default 1000 ms).1000 ms, Cloud Router forces the effective negotiated interval to at least 1000 ms.Min Echo interval: 0 and never uses echo packets.Checking for an inherited BFD multi-hop mismatch would be appropriate if bfd/session_up remained 0 indefinitely and never came up after initial configuration—in which case the fix would be removing ebgp-multihop or explicitly enforcing BFD single-hop 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