300-320 · Question #639
Which EIGRP stub-related statement is correct?
The correct answer is C. You should always configure spoke routers as stubs in hub-and-spoke topology. In a hub-and-spoke topology, configuring spoke routers as EIGRP stubs (Option C) is the recommended best practice. Stub routers advertise only their directly connected and summary routes, preventing spokes from being used as transit paths between other sites. This also limits…
Question
Which EIGRP stub-related statement is correct?
Options
- ARouters configured as stubs automatically summarize all connected routes.
- BWhen remote sites employ two stub routers, each connected to one of the hub routers, remote
- CYou should always configure spoke routers as stubs in hub-and-spoke topology.
- DYou should avoid configuring spoke routers as stubs in hub-and-spoke topology to avoid routing
How the community answered
(18 responses)- B6% (1)
- C94% (17)
Explanation
In a hub-and-spoke topology, configuring spoke routers as EIGRP stubs (Option C) is the recommended best practice. Stub routers advertise only their directly connected and summary routes, preventing spokes from being used as transit paths between other sites. This also limits the scope of EIGRP query propagation - hub routers will not forward queries to stub spokes, dramatically reducing convergence time after a topology change. Option A is false - stub routers do not automatically summarize; summarization must be configured explicitly. Option D is the opposite of best practice - avoiding stub configuration on spokes increases query scope and can cause stuck-in-active (SIA) conditions.
Topics
Community Discussion
No community discussion yet for this question.