- A
Adjust the administrative distance of the floating static route to 201.
Why wrong: The AD is already 200, which is higher than OSPF’s 110, so this change would not prevent OSPF from taking over once it converges. The issue is not the AD but that OSPF is not re‑installing its route.
- B
Check the carrier delay timers on R2's GigabitEthernet0/0 interface.
A high carrier-delay (interface debounce) timer can keep the link down for too long after a flap, delaying OSPF neighbor formation. While the interface remains down, the floating static route stays in the table. Checking this timer is a logical, non‑destructive next step.
- C
Clear the IP routing table and reset the OSPF process on R1.
Why wrong: Clearing the routing table and resetting OSPF is a drastic action that temporarily restores OSPF routes but does not address the underlying reason OSPF failed to converge. It should only be used after confirming the root cause.
- D
Verify that the MTU on R1 and R2's GigabitEthernet0/0 interfaces match.
Why wrong: An MTU mismatch would cause OSPF to be stuck in Exstart/Exchange state, but this would be a persistent problem, not one triggered exclusively by a flap. The described symptom points to a convergence delay, not a permanent adjacency issue.
CCNA IP Routing Practice Question
This 200-301 practice question tests your understanding of ip routing. 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.
R1 loses its route to 192.168.20.0/24 whenever R2's GigabitEthernet0/0 interface flaps. The network engineer has configured a floating static route with an administrative distance of 200. The OSPF route has an AD of 110. After R2's G0/0 interface recovers, the floating static route appears in the routing table instead of the OSPF route. What should the technician do next?
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
Check the carrier delay timers on R2's GigabitEthernet0/0 interface.
The next step is to check the carrier delay timers on R2's G0/0 interface. If a high debounce (carrier-delay) timer is configured, the interface remains down for several seconds after physical link recovery. During this time OSPF neighbor adjacency cannot form, so the floating static route (which is already installed) remains in the table. This is a Layer 2/Layer 1 timing issue that directly impacts OSPF convergence.
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.
- ✗
Adjust the administrative distance of the floating static route to 201.
- ✓
Check the carrier delay timers on R2's GigabitEthernet0/0 interface.
Why this is correct
A high carrier-delay (interface debounce) timer can keep the link down for too long after a flap, delaying OSPF neighbor formation. While the interface remains down, the floating static route stays in the table. Checking this timer is a logical, non‑destructive next step.
Related concept
OSPF neighbours must agree on key parameters.
- ✗
Clear the IP routing table and reset the OSPF process on R1.
Why it's wrong here
Clearing the routing table and resetting OSPF is a drastic action that temporarily restores OSPF routes but does not address the underlying reason OSPF failed to converge. It should only be used after confirming the root cause.
- ✗
Verify that the MTU on R1 and R2's GigabitEthernet0/0 interfaces match.
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.
✓Check the carrier delay timers on R2's GigabitEthernet0/0 interface.Correct answer▾
Why this is correct
A high carrier-delay (interface debounce) timer can keep the link down for too long after a flap, delaying OSPF neighbor formation. While the interface remains down, the floating static route stays in the table. Checking this timer is a logical, non‑destructive next step.
✗Adjust the administrative distance of the floating static route to 201.Wrong answer — click to see why▾
Why this is wrong here
Misunderstanding of route preference: a higher AD value does not keep a floating static installed when a better OSPF route becomes available.
✗Clear the IP routing table and reset the OSPF process on R1.Wrong answer — click to see why▾
Why this is wrong here
Troubleshooting should follow the OSI model bottom‑up; immediately resetting processes skips basic interface‑level verification.
✗Verify that the MTU on R1 and R2's GigabitEthernet0/0 interfaces match.Wrong answer — click to see why▾
Why this is wrong here
It targets a different root cause (OSPF adjacency failure due to MTU) that would manifest constantly, not only after interface recovery.
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.
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.
- →
IP Routing — study guide chapter
Learn the concepts, then practise the questions
- →
IP Routing practice questions
Targeted practice on this topic area only
- →
All 200-301 questions
1,819 questions across all exam domains
- →
CCNA 200-301 v2 study guide
Full concept coverage aligned to exam objectives
- →
200-301 practice test guide
How to use practice tests most effectively before exam day
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.
Network Infrastructure and Connectivity practice questions
Practise 200-301 questions linked to Network Infrastructure and Connectivity.
Switching and Network Access practice questions
Practise 200-301 questions linked to Switching and Network Access.
IP Routing practice questions
Practise 200-301 questions linked to IP Routing.
Network Services and Security practice questions
Practise 200-301 questions linked to Network Services and Security.
AI and Network Operations practice questions
Practise 200-301 questions linked to AI and Network Operations.
CCNA subnetting practice questions
Practise IPv4 subnetting, CIDR, masks, host ranges and subnet selection.
CCNA OSPF practice questions
Practise OSPF neighbours, router IDs, metrics, areas and routing-table interpretation.
CCNA VLAN practice questions
Practise VLANs, access ports, trunks, allowed VLANs and switching scenarios.
CCNA STP practice questions
Practise spanning tree, root bridge election, port roles and STP troubleshooting.
CCNA EtherChannel practice questions
Practise LACP, PAgP, port-channel behaviour and bundle requirements.
CCNA ACL practice questions
Practise standard and extended ACLs, permit/deny logic and traffic filtering.
CCNA NAT practice questions
Practise static NAT, dynamic NAT, PAT and inside/outside address translation.
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?
IP Routing — This question tests IP Routing — OSPF neighbours must agree on key parameters..
What is the correct answer to this question?
The correct answer is: Check the carrier delay timers on R2's GigabitEthernet0/0 interface. — The next step is to check the carrier delay timers on R2's G0/0 interface. If a high debounce (carrier-delay) timer is configured, the interface remains down for several seconds after physical link recovery. During this time OSPF neighbor adjacency cannot form, so the floating static route (which is already installed) remains in the table. This is a Layer 2/Layer 1 timing issue that directly impacts OSPF convergence.
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 →
Keep practising
More 200-301 practice questions
- A switchport connected to another switch should carry multiple VLANs, but it was manually configured as an access port.…
- What problem is HSRP designed to solve?
- Which TWO statements correctly describe the causes or implications of CRC errors, runts, giants, or output errors as see…
- You are connected to R1. Configure IPv4 and IPv6 addressing on R1's interfaces and verify reachability to R2. The curren…
- Which TWO statements accurately describe how AI/ML concepts are applied to network operations in modern enterprise netwo…
- Which TWO switch port configurations are required when connecting a Cisco IP phone and a desktop PC to a single access p…
Last reviewed: Jun 14, 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.