Question 680
An OSPF route appears longer than expected after failover because a backup link's cost was never verified. What is the primary routing or switching concept illustrated?
Explanation
Correct Answer
This option addresses the stated case rather than another networking issue. Principle: Failover paths are governed by their actual configured metrics. Remedy: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs. Proof: When the primary fails the documented backup path is selected without loops.
Incorrect Answers
This answer would be more suitable when a site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency, where the corrective action is to inspect link-state databases and SPF output on affected routers. The failure here is different: Failover paths are governed by their actual configured metrics. Required validation: When the primary fails the documented backup path is selected without loops.
This option overlooks the decisive condition. Its supporting principle is area mismatch can affect Level 1 adjacency even when packets are received, while this scenario depends on failover paths are governed by their actual configured metrics. Verify the correction with: When the primary fails the documented backup path is selected without loops.
The proposed principle concerns another network fault: OSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone. Here, failover paths are governed by their actual configured metrics. The most direct correction is to confirm the explicit cost plan in a failure rehearsal using route and topology outputs, confirmed by when the primary fails the documented backup path is selected without loops.