4A0-102 · Question #75
Which of the following routes is NOT considered an internal route?
The correct answer is C. A route received from a BGP peer from a different member AS of a confederation. Option C is the correct answer because routes exchanged between different member ASes within a BGP confederation use confederation eBGP - they cross sub-AS boundaries, carry confederation AS_PATH attributes, and behave like external routes, so they are not classified as…
Question
Options
- AA route received from a BGP peer within the same AS.
- BA route originated by a router in a different cluster of the same AS.
- CA route received from a BGP peer from a different member AS of a confederation.
- DA route received from a BGP peer from the same member AS of a confederation.
How the community answered
(27 responses)- A4% (1)
- B7% (2)
- C78% (21)
- D11% (3)
Explanation
Option C is the correct answer because routes exchanged between different member ASes within a BGP confederation use confederation eBGP - they cross sub-AS boundaries, carry confederation AS_PATH attributes, and behave like external routes, so they are not classified as internal routes in the traditional iBGP sense.
Why the distractors are wrong:
- A is clearly internal: a peer in the same AS communicates via iBGP by definition.
- B is internal: Route Reflector clusters are an intra-AS mechanism; routes between clusters still live entirely within one AS.
- D is internal: peers within the same confederation member AS use iBGP, making those routes internal just like any standard iBGP route.
Memory tip: Use the rule "same = internal." Same AS, same cluster, same confederation member AS → internal. The moment you cross into a different confederation member AS, you've crossed a sub-AS boundary (confederation eBGP), which breaks the "same" rule and makes the route non-internal. C is the only option that crosses that boundary.
Topics
Community Discussion
No community discussion yet for this question.