Arrange the following OSPF status changes under the Broadcast network type in the correct order: Exchange, Attempt, Init, Loading, Full, ExStart, 2-way, Down

Question

Options

• ADown, Init, 2-way, ExStart, Loading, Full, Exchange
• B
• C
• D

• A
  82% (23)
• B
  4% (1)
• C
  4% (1)
• D
  11% (3)

Explanation

Option A is marked correct, but as written it contains a likely typo - Exchange appears after Full, which is wrong. The actual correct OSPF neighbor state sequence for a Broadcast network type is:

Down → Init → 2-Way → ExStart → Exchange → Loading → Full

Why this order:

• Down: No Hellos received yet
• Init: Hello received, but your Router ID isn't in the neighbor's Hello yet (one-way)
• 2-Way: Bidirectional communication confirmed; DR/BDR election occurs here
• ExStart: Master/Slave negotiated; DBD sequence numbers established
• Exchange: Full DBD (Database Description) packets exchanged
• Loading: Missing LSAs requested and received via LSR/LSU
• Full: LSDB fully synchronized - adjacency complete

Why "Attempt" is excluded: Attempt only applies to NBMA network types where neighbors are manually configured. It does not appear in Broadcast neighbor formation.

Memory tip: Use the mnemonic "Down In ExStart, Everyone Loads Full" → Down, Init, 2-way, ExStart, Exchange, Loading, Full. Think of it as two phases: discovery (Down→2-Way) and database sync (ExStart→Full).

No community discussion yet for this question.