Through the linkage between BFD and MPLS LSP, BFD can be dynamically created to detect the connectivity of static or dynamic LSP.

Question

Options

• ATRUE
• BFALSE

• A
  79% (41)
• B
  21% (11)

Explanation

A is correct because BFD (Bidirectional Forwarding Detection) supports a linkage mechanism with MPLS LSPs that enables BFD sessions to be dynamically created - meaning they are automatically established and torn down in response to LSP state changes, rather than requiring manual configuration of each BFD session. This applies to both static LSPs (manually provisioned) and dynamic LSPs (established via signaling protocols like LDP or RSVP-TE), giving network operators a unified failure-detection tool across both LSP types.

B is incorrect because it denies the existence of this dynamic binding capability, which is a well-defined feature in modern implementations (standardized in RFC 5884 for MPLS LSP BFD). Without this linkage, operators would need to manually configure BFD sessions for every LSP, which is impractical at scale.

Memory tip: Think of BFD-LSP linkage as a "shadow" - just as a shadow automatically appears and disappears with the object that casts it, a BFD session automatically follows the lifecycle of its associated LSP (both static and dynamic). If the LSP exists, BFD watches it; if the LSP is gone, BFD cleans up too.

No community discussion yet for this question.