Question 595 of 1,819
AI and Network OperationshardTroubleshootingObjective-mapped

Quick Answer

The answer is to use the 'show ip ospf neighbor' command to check the neighbor state, and if it is not FULL, then examine 'show ip ospf interface' for mismatched hello/dead intervals or network type. This is correct because OSPF requires consistent hello and dead intervals, as well as a matching network type, on both sides of a link to form a full adjacency; if these parameters are misaligned, the routers will stall in states like INIT, 2-WAY, or EXSTART, preventing route exchange. On the CCNA 200-301 v2 exam, this scenario tests your ability to troubleshoot OSPF neighbor issues after a protocol change, often appearing as a simulation where you must identify why routes are missing after switching from EIGRP to OSPF. A common trap is forgetting that the default hello interval differs between network types—for example, broadcast networks use 10 seconds, while point-to-point uses 30 seconds. Memory tip: "Hello and dead must match, or the neighbor won't hatch."

CCNA AI and Network Operations Practice Question

This 200-301 practice question tests your understanding of ai and network operations. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Network Topology
G0/010.0.1.1/30G0/010.0.1.2/30linkG0/1192.168.1.1/24linkR1R2SW1

You are connected to R1 via the console. R1 is a Cisco ISR 4321 router running IOS-XE. The network team has recently changed the routing protocol from EIGRP to OSPF, but some routes are missing from the routing table. You need to analyze the OSPF neighbor states and LSDB to identify the issue.

Question 1hardTroubleshooting
Review the full OSPF breakdown →

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

Use 'show ip ospf neighbor' to check neighbor state; if not FULL, examine 'show ip ospf interface' for mismatched hello/dead intervals or network type.

OSPF requires consistent hello/dead intervals and network types to form adjacency. If the neighbor is not in FULL state, routes will not be exchanged. Checking 'show ip ospf neighbor' reveals the state; mismatched parameters can be corrected by adjusting interface configuration.

Key principle: OSPF neighbour adjacency depends on matching area, hello/dead timers, network type, and authentication — IP reachability alone is not enough.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Use 'show ip ospf neighbor' to check neighbor state; if not FULL, examine 'show ip ospf interface' for mismatched hello/dead intervals or network type.

    Why this is correct

    This is correct because OSPF requires consistent hello/dead intervals and network types to form a FULL adjacency. The 'show ip ospf neighbor' command reveals the neighbor state, and 'show ip ospf interface' shows the configured parameters. If mismatched, routes will not be exchanged.

    Related concept

    OSPF neighbours must agree on key parameters.

  • Use 'show ip route ospf' to verify OSPF routes; if missing, re-enter the OSPF process and redistribute connected routes.

    Why it's wrong here

    This is incorrect because 'show ip route ospf' only displays routes that are already in the routing table; it does not help identify why adjacencies are not forming. Re-entering the OSPF process or redistributing connected routes does not address the root cause of missing adjacencies.

  • Use 'debug ip ospf events' to monitor OSPF packets; if no packets are seen, reconfigure OSPF router ID and clear the OSPF process.

    Why it's wrong here

    This is incorrect because while 'debug ip ospf events' can show OSPF packet exchanges, it is a high-overhead command and not the first step in troubleshooting. Reconfiguring the router ID and clearing the OSPF process is disruptive and may not resolve mismatched parameters.

  • Use 'show ip protocols' to verify OSPF process configuration; if incorrect, delete and recreate the OSPF process with the correct network statements.

    Why it's wrong here

    This is incorrect because 'show ip protocols' shows routing protocol configuration but does not reveal interface-level mismatches like hello/dead intervals or network type. Deleting and recreating the OSPF process is an extreme measure that may not fix the specific issue.

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.

Use 'show ip ospf neighbor' to check neighbor state; if not FULL, examine 'show ip ospf interface' for mismatched hello/dead intervals or network type.Correct answer

Why this is correct

This is correct because OSPF requires consistent hello/dead intervals and network types to form a FULL adjacency. The 'show ip ospf neighbor' command reveals the neighbor state, and 'show ip ospf interface' shows the configured parameters. If mismatched, routes will not be exchanged.

Use 'show ip route ospf' to verify OSPF routes; if missing, re-enter the OSPF process and redistribute connected routes.Wrong answer — click to see why

Why this is wrong here

The specific factual error is that 'show ip route ospf' shows only existing OSPF routes, not neighbor states. Redistribution is not needed for directly connected interfaces in the same OSPF area.

Why candidates choose this

Candidates pick this because they think missing routes are due to redistribution issues, but the problem is likely at the adjacency level.

Use 'debug ip ospf events' to monitor OSPF packets; if no packets are seen, reconfigure OSPF router ID and clear the OSPF process.Wrong answer — click to see why

Why this is wrong here

The specific factual error is that debugging is not the initial diagnostic step; it should be used after verifying neighbor states and interface parameters. Changing the router ID is unnecessary unless there is a duplicate router ID issue.

Why candidates choose this

Candidates pick this because debugging seems like a direct way to see OSPF activity, but it is resource-intensive and often not needed for basic parameter mismatches.

Use 'show ip protocols' to verify OSPF process configuration; if incorrect, delete and recreate the OSPF process with the correct network statements.Wrong answer — click to see why

Why this is wrong here

The specific factual error is that 'show ip protocols' does not display per-interface OSPF parameters. The problem is likely at the interface level, not the process level.

Why candidates choose this

Candidates pick this because they assume the OSPF process configuration is incorrect, but the issue is more likely mismatched interface parameters between neighbors.

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?”

Common exam traps

Common exam trap: OSPF can fail even when IP connectivity looks correct

OSPF neighbour formation depends on matching areas, timers, network type, authentication and passive-interface behaviour. Do not choose an answer only because the devices can ping.

Trap categories for this question

  • Command / output trap

    This is incorrect because 'show ip route ospf' only displays routes that are already in the routing table; it does not help identify why adjacencies are not forming. Re-entering the OSPF process or redistributing connected routes does not address the root cause of missing adjacencies.

Detailed technical explanation

How to think about this question

OSPF questions usually test the details that control adjacency and route selection. Read the neighbour state, area, router ID and interface configuration before deciding what is wrong.

KKey Concepts to Remember

  • OSPF neighbours must agree on key parameters.
  • Router ID selection can affect neighbour relationships and LSDB output.
  • OSPF cost influences the preferred path.
  • A route can appear in OSPF information but not become the installed route.

TExam Day Tips

  • Check area mismatch first when OSPF adjacency fails.
  • Review passive interfaces when a network is advertised but no neighbour forms.
  • Use show ip ospf neighbor and show ip route clues carefully.

Key takeaway

OSPF neighbour adjacency depends on matching area, hello/dead timers, network type, and authentication — IP reachability alone is not enough.

Real-world example

How this comes up in practice

A network engineer at a university connects two campus buildings via a fibre link. Both routers run OSPF, but no adjacency forms — even though both routers can ping each other. The engineer finds one router is in area 0 and the other in area 1. OSPF adjacency requires matching area numbers, hello/dead timers, and network type. IP reachability alone is not enough.

What to study next

Got this wrong? Here's your next step.

Review OSPF neighbour requirements — matching area type, hello and dead timers, network type, stub flags, and authentication. Study show ip ospf neighbor states (INIT, 2-WAY, FULL). Then practise related 200-301 OSPF questions on adjacency and route selection.

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.

Practice this exam

Start a free 200-301 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this 200-301 question test?

AI and Network Operations — This question tests AI and Network Operations — OSPF neighbours must agree on key parameters..

What is the correct answer to this question?

The correct answer is: Use 'show ip ospf neighbor' to check neighbor state; if not FULL, examine 'show ip ospf interface' for mismatched hello/dead intervals or network type. — OSPF requires consistent hello/dead intervals and network types to form adjacency. If the neighbor is not in FULL state, routes will not be exchanged. Checking 'show ip ospf neighbor' reveals the state; mismatched parameters can be corrected by adjusting interface configuration.

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

Review OSPF neighbour requirements — matching area type, hello and dead timers, network type, stub flags, and authentication. Study show ip ospf neighbor states (INIT, 2-WAY, FULL). Then practise related 200-301 OSPF questions on adjacency and route selection.

What is the key concept behind this question?

OSPF neighbours must agree on key parameters.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More 200-301 practice questions

Last reviewed: Jun 7, 2026

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.

Loading comments…

Sign in to join the discussion.

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.