H12-821_V1.0 · Question #822
BFD itself does not have a neighbor discovery mechanism, but relies on the upper-layer application being served to notify its neighbor information to establish a session.
The correct answer is A. TRUE. Option A is correct because BFD (Bidirectional Forwarding Detection) is intentionally designed as a lightweight, fast failure-detection protocol - neighbor discovery would add complexity that is outside its scope. Instead, BFD depends entirely on upper-layer protocols (such as…
Question
Options
- ATRUE
- BFALSE
How the community answered
(70 responses)- A83% (58)
- B17% (12)
Explanation
Option A is correct because BFD (Bidirectional Forwarding Detection) is intentionally designed as a lightweight, fast failure-detection protocol - neighbor discovery would add complexity that is outside its scope. Instead, BFD depends entirely on upper-layer protocols (such as OSPF, BGP, IS-IS, or static routing) to identify a neighbor and trigger BFD session creation via a notification or API call.
Option B is wrong because the statement is an accurate description of BFD's architecture - there is no built-in discovery mechanism like Hello packets used for neighbor detection; BFD sessions are always bootstrapped by an external application.
Memory tip: Think of BFD as a watchdog timer, not a relationship builder. Routing protocols (OSPF, BGP, etc.) introduce the neighbors; BFD just watches over them once introduced. "BFD detects, it doesn't discover."
Topics
Community Discussion
No community discussion yet for this question.