Which of the following regarding the connections between eBGP peers is TRUE?

Question

Options

• AeBGP peers typically use system addresses for session establishment.
• BeBGP peers are managed under a single administration.
• CeBGP peers do not propagate updates learned via iBGP.
• DeBGP peers are usually directly connected to each other.

• A
  4% (1)
• B
  4% (1)
• C
  4% (1)
• D
  88% (23)

Explanation

eBGP (External BGP) peers reside in different Autonomous Systems and are usually directly connected - the default TTL for eBGP packets is 1, meaning packets expire after one hop, so a direct physical link is the standard expectation (though ebgp-multihop can override this).

Why the distractors are wrong:

• A is false - loopback/system addresses are the norm for iBGP sessions (within an AS), not eBGP, precisely because iBGP peers aren't required to be directly connected.
• B describes iBGP - peers under a single administrative domain share an AS number; eBGP by definition spans different ASes with separate administrations.
• C is backwards - eBGP does propagate routes learned via iBGP (and vice versa); this is fundamental to how inter-AS routing works. The real restriction is that iBGP peers won't re-advertise routes to other iBGP peers (split horizon rule).

Memory tip: Think of eBGP as a handshake at the border - two neighbors reaching across a fence directly. iBGP is the internal memo system that uses stable loopback addresses because it travels through the building.

No community discussion yet for this question.