Question 350
An OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange. What implementation step and validation result should be selected?
Explanation
Correct Answer
Correct diagnosis: Neighbor discovery can succeed even when database exchange parameters prevent completion. The appropriate action is: Check MTU and interface compatibility and inspect neighbor-state details. The follow-up evidence required is: The adjacency advances through database synchronization to Full.
Incorrect Answers
The alternative addresses after a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors, not the present root cause. Here the selected correction must reflect neighbor discovery can succeed even when database exchange parameters prevent completion. Test for: The adjacency advances through database synchronization to Full.
This answer would be more suitable when a provider exports an unexpectedly broad set of routes into OSPF after accepting a generic routing policy, where the corrective action is to constrain redistribution and test route policy acceptance for the intended prefixes. The failure here is different: Neighbor discovery can succeed even when database exchange parameters prevent completion. Required validation: The adjacency advances through database synchronization to Full.
This option overlooks the decisive condition. Its supporting principle is oSPF neighbor-state interpretation depends on multiaccess election roles, while this scenario depends on neighbor discovery can succeed even when database exchange parameters prevent completion. Verify the correction with: The adjacency advances through database synchronization to Full.