400-007 · Question #166
What advantage of placing the IS-IS layer 2 flooding domain boundary at the core Layer in a three- layer hierarchical network is true?
The correct answer is D. The Layer 2 domain is contained and more stable. Placing the IS-IS Level 2 flooding domain boundary at the core layer limits LSP propagation scope, improving stability and predictability of the backbone routing domain.
Question
What advantage of placing the IS-IS layer 2 flooding domain boundary at the core Layer in a three- layer hierarchical network is true?
Options
- AThe Layer 1 and Layer 2 domains can easily overlap
- BIt reduces the complexity of the Layer 1 domains
- CIt can be applied to any kind of topology
- DThe Layer 2 domain is contained and more stable
How the community answered
(40 responses)- A15% (6)
- B8% (3)
- C5% (2)
- D73% (29)
Why each option
Placing the IS-IS Level 2 flooding domain boundary at the core layer limits LSP propagation scope, improving stability and predictability of the backbone routing domain.
Level 1 and Level 2 domains are by definition separate in IS-IS; overlapping them is not an advantage of this design choice.
Placing the boundary at the core does not simplify Level 1 domains - Level 1 complexity is determined by the number of routers and links within each area, independent of where the Level 2 boundary sits.
This boundary placement is specifically suited to hierarchical three-layer topologies and is not universally applicable to any kind of topology.
When the Level 2 domain boundary is placed at the core, Level 2 LSPs are confined to core routers only, reducing the size of the Level 2 LSDB and preventing churn from access or distribution topology changes from propagating into the backbone. This containment makes the Level 2 domain smaller, faster to converge, and more stable overall.
Concept tested: IS-IS Level 2 flooding domain placement in hierarchical design
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_isis/configuration/xe-17/iri-xe-17-book/iri-overview.html
Topics
Community Discussion
No community discussion yet for this question.