Question 500
A core network change board wants to avoid: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only. Which ongoing safeguard fits best?
Explanation
Correct Answer
Add a common-level check to link commissioning scripts. This helps prevent recurrence of the issue: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only. Acceptance evidence should be: A lab peering test establishes a stable adjacency and exchanges the intended LSPs.
Incorrect Answers
Validate NET configuration and IS-IS levels during provisioning. That is a sensible control for ANOTHER scenario: A core interface comes up but its IS-IS hellos never result in adjacency because peer system IDs use incompatible area addressing on L1-only neighbors. It is less targeted to this issue than: Add a common-level check to link commissioning scripts.
Document each node's IS-IS level and area role before topology extensions. That is a sensible control for ANOTHER scenario: Two provider core routers form an IS-IS L1 adjacency but do not exchange a prefix from another area because the engineer assumes L1 routers have universal interarea visibility. It is less targeted to this issue than: Add a common-level check to link commissioning scripts.
Use a peer inventory to preflight local and remote AS values. That is a sensible control for ANOTHER scenario: A new eBGP handoff establishes TCP transport but remains Idle/Active because the peer configuration uses the wrong autonomous-system number. It is less targeted to this issue than: Add a common-level check to link commissioning scripts.