Question 1,643 of 1,389
CCNA IP Routing Practice Question
Two routers are in the same OSPF area and on the same subnet, but they do not form an adjacency. One interface uses a hello interval of 10 seconds and the other uses 5 seconds. What is the most likely cause?
⚠ Common exam trap
A common exam trap is assuming that because two routers can ping each other on the same subnet, their OSPF adjacency will form automatically. The trap lies in overlooking the importance of matching OSPF hello and dead timers. Many candidates focus only on IP addressing or area configuration and miss that OSPF requires exact timer agreement. This leads to confusion when adjacency never forms despite correct IP setup. The exam tests your understanding that OSPF is a protocol with strict neighbor parameter requirements, not just IP reachability.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The OSPF hello timers do not match.
An OSPF timer mismatch is the most likely cause. In plain language, the routers are trying to discover each other, but they are speaking on different timing expectations. OSPF neighbors on the same segment must agree on certain parameters before they trust each other enough to form an adjacency, and the hello and dead timers are among those critical values. This is a very common OSPF troubleshooting issue because the interfaces may still be reachable with ping and may even appear correctly addressed and placed in the same area. But OSPF is stricter than simple IP reachability. If the hello interval does not match, the adjacency usually fails before it becomes fully operational.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The OSPF hello timers do not match.
Why this is correct
OSPF requires neighboring routers to agree on hello and dead intervals to form and maintain adjacency. If hello timers do not match, the router will not accept the neighbor's Hello packets within the dead interval, causing the Dead Timer to expire and preventing adjacency. This specific mismatch is a classic cause when two routers are in the same area and subnet but cannot see each other as OSPF neighbors.
- ✗
The routers need matching hostnames.
Why it's wrong here
OSPF router identification does not depend on hostnames; instead, it uses the Router ID, which is derived from the highest configured loopback IPv4 address or the highest IPv4 address on a physical interface. Hostnames are merely labels for configuration convenience and are not exchanged in OSPF Hello packets. Matching hostnames is never a condition for OSPF adjacency formation.
When this WOULD be correct
In a different scenario where the question asks about OSPF configuration issues related to hostname resolution, a candidate might be asked why two routers with mismatched hostnames cannot communicate properly. In that case, if hostname resolution is a factor, this option could be correct.
- ✗
The subnet must be changed to /24 before OSPF can work.
Why it's wrong here
OSPF is classless and supports variable-length subnet masks (VLSM), so it can operate on any prefix length, including /24, /30, or /16, depending on the design. Changing the subnet to /24 would not resolve a hello timer mismatch, because the real cause is at Layer 3 OSPF parameters, not the subnet mask. In fact, altering the subnet mask could break IP addressing if the current subnet is deliberately sized.
When this WOULD be correct
In a different scenario where the question states that two routers are on different subnets, and OSPF is configured, a candidate might choose this option if they believe that changing the subnet to /24 would allow the routers to communicate and form an adjacency.
- ✗
The routers must both use static routes first.
Why it's wrong here
OSPF is a dynamic routing protocol that builds its routing table using link-state advertisements and the SPF algorithm; static routes are not required for it to establish neighbor adjacencies. The two routers can form an OSPF adjacency without any static route configuration, and static routes would only be relevant to forwarding traffic, not to protocol operation. Therefore, this option incorrectly introduces a prerequisite that does not exist for OSPF.
When this WOULD be correct
In a different scenario, if a question states that two routers are configured to use OSPF but are unable to establish an adjacency due to missing static routes that are required for initial connectivity, then this option would be correct.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.
✓The OSPF hello timers do not match.Correct answer▾
Why this is correct
OSPF requires neighboring routers to agree on hello and dead intervals to form and maintain adjacency. If hello timers do not match, the router will not accept the neighbor's Hello packets within the dead interval, causing the Dead Timer to expire and preventing adjacency. This specific mismatch is a classic cause when two routers are in the same area and subnet but cannot see each other as OSPF neighbors.
✗The routers need matching hostnames.Wrong answer — click to see why▾
Why this is wrong here
This option is incorrect because OSPF does not require matching hostnames for routers to form an adjacency; it relies on matching OSPF parameters like hello and dead intervals.
★ When this WOULD be the correct answer
In a different scenario where the question asks about OSPF configuration issues related to hostname resolution, a candidate might be asked why two routers with mismatched hostnames cannot communicate properly. In that case, if hostname resolution is a factor, this option could be correct.
Why candidates choose this
Candidates may mistakenly believe that hostnames play a critical role in OSPF adjacency formation, especially if they are familiar with other protocols where hostnames are significant for communication.
✗The subnet must be changed to /24 before OSPF can work.Wrong answer — click to see why▾
Why this is wrong here
The subnet mask does not affect OSPF adjacency formation as long as both routers are in the same subnet. OSPF can operate correctly with any valid subnet mask that includes both routers.
★ When this WOULD be the correct answer
In a different scenario where the question states that two routers are on different subnets, and OSPF is configured, a candidate might choose this option if they believe that changing the subnet to /24 would allow the routers to communicate and form an adjacency.
Why candidates choose this
Candidates may mistakenly believe that subnet configuration is critical for OSPF adjacency, leading them to choose this option due to a lack of understanding of OSPF's requirements for adjacency beyond subnetting.
✗The routers must both use static routes first.Wrong answer — click to see why▾
Why this is wrong here
This option is wrong because OSPF can operate without static routes; adjacency issues are typically related to OSPF configuration parameters rather than routing methods.
★ When this WOULD be the correct answer
In a different scenario, if a question states that two routers are configured to use OSPF but are unable to establish an adjacency due to missing static routes that are required for initial connectivity, then this option would be correct.
Why candidates choose this
Candidates might choose this option due to a misunderstanding of OSPF's requirements, mistakenly believing that static routes are necessary for OSPF to function properly in all cases.
Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Visual reference
Quick reference
Routing Protocol Comparison
| Protocol | Metric | Max Hops | Algorithm | Type |
|---|---|---|---|---|
| RIP v2 | Hop count | 15 | Bellman-Ford | Distance vector |
| OSPF | Cost (bandwidth) | Unlimited | Dijkstra (SPF) | Link state |
| EIGRP | Composite metric | Unlimited | DUAL | Hybrid |
| IS-IS | Cost | Unlimited | Dijkstra | Link state |
| BGP | Policy / attributes | Unlimited | Path vector | Path vector |
RIP's 15-hop limit makes it unsuitable for large networks. OSPF and EIGRP dominate modern enterprise deployments.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: May 17, 2026
This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.