This 300-410 practice question tests your understanding of mpls operations. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. 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.
A DMVPN network with EIGRP as the routing protocol experiences spoke-to-spoke tunnel failures. Hub router R1 has configuration: 'interface Tunnel0 ip nhrp network-id 1 ip nhrp map multicast dynamic ip nhrp redirect' and 'router eigrp 100 network 10.0.0.0'. Spoke router R2 shows 'show ip nhrp brief' output: '10.0.0.1/32 via 192.168.1.1, Tunnel0 created 00:10:00, dynamic' but 'show ip eigrp neighbors' shows only the hub. What is the root cause?
Spoke-to-spoke tunnels require NHRP redirect and shortcut features to trigger direct communication. The hub has 'ip nhrp redirect' but spokes must have 'ip nhrp shortcut' to install direct routes. Without this, spokes only communicate via hub, causing suboptimal routing and potential failure if hub is overloaded.
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.
EIGRP is not configured to advertise the tunnel network; need 'network 10.0.0.0' on spokes.
Why it's wrong here
EIGRP is already configured; neighbors are formed with hub.
✗
The hub router needs 'ip nhrp map multicast dynamic' to forward multicast for EIGRP; it is already present.
Why it's wrong here
Multicast forwarding works as hub sees spokes.
✗
NHRP authentication mismatch between hub and spokes causes NHRP registration failure.
Why it's wrong here
NHRP registration succeeds as shown in NHRP brief.
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
NHRP registration succeeds as shown in NHRP brief.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this 300-410 question in full detail.
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 300-410 OSPF questions on adjacency and route selection.
MPLS Operations — This question tests MPLS Operations — OSPF neighbours must agree on key parameters..
What is the correct answer to this question?
The correct answer is: Spoke routers are missing 'ip nhrp shortcut' interface configuration, preventing dynamic spoke-to-spoke tunnel establishment. — Spoke-to-spoke tunnels require NHRP redirect and shortcut features to trigger direct communication. The hub has 'ip nhrp redirect' but spokes must have 'ip nhrp shortcut' to install direct routes. Without this, spokes only communicate via hub, causing suboptimal routing and potential failure if hub is overloaded.
What should I do if I get this 300-410 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 300-410 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 →
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.
This 300-410 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 300-410 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.