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
  Network Type POINT_TO_POINT

R2# show ip ospf interface g0/0
GigabitEthernet0/0 is up, line protocol is up
  Internet Address 10.1.12.2/30, Area 0
  Network Type BROADCAST

A router pair is directly connected, but they do not become OSPF neighbors. IP addressing and area assignment are correct. Based on the output, what is the most likely cause?

Question 1hardmultiple choice
Full question →

A router pair is directly connected, but they do not become OSPF neighbors. IP addressing and area assignment are correct. Based on the output, 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

OSPF network type mismatch on the connected interfaces

This is correct because one side is using point-to-point and the other is using broadcast, which can prevent a stable adjacency.

B

Distractor review

Duplicate default routes on both routers

This is wrong because the issue described is neighbor formation, not route selection involving default routes.

C

Distractor review

Missing VLAN trunking on the link

This is wrong because the interfaces shown are routed OSPF interfaces, not switch trunks.

D

Distractor review

The OSPF process IDs are required to match

This is wrong because OSPF process IDs are locally significant.

Common exam trap

Common exam trap: answer the scenario, not the keyword

A common exam trap is assuming that OSPF process IDs must match on both routers to form neighbors. Many candidates mistakenly believe process IDs are globally significant, but they are only locally important identifiers. Another tempting mistake is blaming IP addressing or area mismatches without checking the OSPF network type. Since network type controls how OSPF hellos are sent and received, a mismatch between broadcast and point-to-point types can silently block adjacency formation even when IP and area configurations appear correct. This subtlety often leads to confusion during troubleshooting and exam scenarios.

Technical deep dive

How to think about this question

OSPF (Open Shortest Path First) is a link-state routing protocol that forms neighbor adjacencies between routers on directly connected networks. One critical parameter for adjacency formation is the OSPF network type configured on the interfaces. Network types define how OSPF treats the link, such as broadcast, point-to-point, point-to-multipoint, or non-broadcast multi-access (NBMA). These types influence the hello and dead intervals, DR/BDR election, and neighbor discovery mechanisms. For two routers to become OSPF neighbors, their network types on the connected interfaces must match. If one router treats the link as broadcast (expecting DR/BDR elections and multicast hellos) and the other treats it as point-to-point (no DR/BDR, unicast hellos), the hello packets and neighbor expectations will not align, preventing adjacency formation. This mismatch causes the routers to see each other but never establish full neighbor states despite correct IP addressing and area assignments. This scenario is a common CCNA exam trap because candidates often verify IP addressing and area IDs but overlook network type consistency. Practically, mismatched network types cause OSPF adjacency failures even when physical connectivity is perfect. Cisco IOS allows manual configuration of network types, so understanding this behavior helps troubleshoot adjacency issues in lab and production environments.

KKey Concepts to Remember

  • OSPF requires matching network types on connected interfaces to successfully form neighbor adjacencies and exchange routing information.
  • The OSPF network type determines hello packet behavior, DR/BDR election, and neighbor discovery mechanisms on a link.
  • A mismatch between broadcast and point-to-point network types prevents OSPF routers from establishing stable adjacencies despite correct IP and area settings.
  • OSPF process IDs are locally significant and do not need to match for neighbor relationships to form.
  • Duplicate default routes do not affect OSPF neighbor formation but influence routing decisions after adjacency is established.
  • VLAN trunking is irrelevant for routed OSPF interfaces because OSPF operates at Layer 3, not Layer 2 switching.
  • OSPF adjacency failures due to network type mismatches often show interfaces up and in the same subnet but no neighbor state progression.
  • Correctly configuring OSPF network types ensures consistent hello intervals and neighbor expectations, enabling adjacency formation.

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 requires matching network types on connected interfaces to successfully form neighbor adjacencies and exchange routing information.

What is the correct answer to this question?

The correct answer is: OSPF network type mismatch on the connected interfaces — The most likely cause is an OSPF network type mismatch. In plain language, the routers are connected and trying to run OSPF, but they do not agree on how the link should behave from OSPF’s perspective. OSPF expects several adjacency-related parameters to align, and network type is one of them. If one side treats the segment as point-to-point and the other treats it as broadcast, the hello process and neighbor expectations do not line up cleanly. This is a classic CCNA troubleshooting pattern because the obvious items such as IP addressing and area membership can still look correct. The real clue is hidden in the interface-level OSPF output. When the network type differs, adjacency formation can fail even though the interfaces are up and the routers are in the same subnet. That makes the network-type mismatch the most defensible answer.

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.