hardmultiple choiceObjective-mapped

Exhibit

R1# show ip ospf interface g0/0
GigabitEthernet0/0 is up, line protocol is up
  Internet Address 10.1.12.1/30, Area 0
  MTU 1500 bytes

R2# show ip ospf interface g0/0
GigabitEthernet0/0 is up, line protocol is up
  Internet Address 10.1.12.2/30, Area 0
  MTU 1400 bytes

R1 and R2 are directly connected and running OSPF. The IP addressing is correct and both routers are in area 0, but they do not form an adjacency. Based on the exhibit, what is the most likely cause?

Question 1hardmultiple choice
Full question →

R1 and R2 are directly connected and running OSPF. The IP addressing is correct and both routers are in area 0, but they do not form an adjacency. Based on the exhibit, what is the most likely cause?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

The OSPF MTU values do not match on the connected interfaces.

This is correct because MTU mismatch is a known cause of OSPF adjacency problems during database exchange.

B

Distractor review

The routers must use identical hostnames before OSPF can form neighbors.

This is wrong because hostnames do not determine OSPF adjacency.

C

Distractor review

The routers must use VLAN 1 for OSPF to operate.

This is wrong because OSPF is not dependent on VLAN 1 in this routed-interface scenario.

D

Distractor review

The interfaces need to be configured as trunks instead of routed ports.

This is wrong because OSPF commonly runs over routed interfaces, not switch trunks.

Common exam trap

Common exam trap: answer the scenario, not the keyword

A common exam trap is assuming that because routers can ping each other and share the same OSPF area, adjacency must form correctly. This overlooks the critical role of MTU matching. Candidates may mistakenly believe hostname matching or VLAN configurations affect OSPF adjacency, but these do not influence OSPF neighbor formation. The subtlety of MTU mismatch causing adjacency failure during database exchange is often missed, leading to incorrect troubleshooting steps or answer choices. Recognizing that OSPF adjacency depends on interface parameters beyond basic IP connectivity is key to avoiding this trap.

Technical deep dive

How to think about this question

OSPF (Open Shortest Path First) is a link-state routing protocol that establishes neighbor adjacencies to exchange routing information within the same area. For two routers to form an OSPF adjacency, several parameters must match, including area ID, hello and dead intervals, authentication settings, and importantly, the MTU (Maximum Transmission Unit) size on the interfaces. The MTU defines the largest packet size that can be transmitted without fragmentation. If the MTU values differ, OSPF adjacency formation can stall during the database exchange phase because routers reject packets that exceed their MTU size. During OSPF neighbor establishment, routers first exchange hello packets to discover neighbors and verify basic parameters. Once neighbors are recognized, they proceed to exchange link-state databases. If the MTU sizes do not match, the routers detect this mismatch and prevent the adjacency from fully forming to avoid packet loss or fragmentation issues. This behavior is specific to OSPF and is a common troubleshooting point when IP connectivity and area configurations appear correct but adjacency fails. The exam trap here is assuming that IP connectivity and matching area IDs guarantee OSPF adjacency. In reality, OSPF adjacency depends on multiple interface parameters, and MTU mismatch is a subtle but critical factor. Practically, routers can ping each other because ICMP packets are smaller and less sensitive to MTU differences, but OSPF adjacency fails because OSPF packets during database exchange are larger and require matching MTU. Understanding this nuance is essential for CCNA candidates to diagnose adjacency issues effectively.

KKey Concepts to Remember

  • OSPF routers must have matching MTU values on connected interfaces to successfully form neighbor adjacencies and exchange routing information.
  • OSPF adjacency formation involves multiple parameters including area ID, hello/dead intervals, authentication, and MTU size, all of which must align.
  • An MTU mismatch prevents OSPF routers from completing the database exchange phase, causing adjacency to remain in the INIT or EXSTART state.
  • Basic IP connectivity and correct subnetting do not guarantee OSPF adjacency if interface parameters like MTU differ between neighbors.
  • OSPF hello packets verify neighbor presence, but the adjacency fully forms only after successful database synchronization, which MTU mismatch can block.
  • Routers do not need identical hostnames for OSPF adjacency; hostname differences do not affect OSPF neighbor relationships.
  • OSPF operates over routed interfaces and does not require VLAN 1 or trunk configurations to form adjacencies on point-to-point links.
  • Understanding MTU mismatch as a cause of adjacency failure helps avoid misdiagnosing OSPF neighbor issues that appear as connectivity problems.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Related practice questions

Related 200-301 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this 200-301 question test?

OSPF routers must have matching MTU values on connected interfaces to successfully form neighbor adjacencies and exchange routing information.

What is the correct answer to this question?

The correct answer is: The OSPF MTU values do not match on the connected interfaces. — The most likely cause is an MTU mismatch between the two interfaces. In practical terms, the routers can still ping each other and appear correctly configured for OSPF at first glance, but adjacency formation involves more than basic IP connectivity. During the database exchange process, OSPF expects key interface characteristics to align, and MTU is one of the values that can stop the relationship from progressing normally. This is a classic CCNA troubleshooting scenario because the problem is subtle. The interfaces are up, the subnet is correct, and the area matches. But OSPF neighbors can still get stuck during formation if one side expects larger packets than the other side is willing to process. That makes the MTU mismatch the strongest answer here.

What should I do if I get this 200-301 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.