hardMultiple ChoiceObjective-mapped
300-410 Practice Question: Configures redistribution between OSPF and EIGRP…
A network engineer configures redistribution between OSPF and EIGRP on a multi-access link. After configuration, OSPF neighbors keep flapping. Router R1 config:
interface GigabitEthernet0/0 ip ospf network broadcast ip ospf hello-interval 10
!
router ospf 1
redistribute eigrp 100 subnets !
router eigrp 100
redistribute ospf 1 metric 10000 100 255 1 1500
R1# show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 192.168.1.2 1 FULL/DR 00:00:35 10.1.1.2 GigabitEthernet0/0 192.168.1.3 1 2WAY/DROTHER 00:00:31 10.1.1.3 GigabitEthernet0/0
What is the root cause?
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 interval is too low, causing neighbor flapping under load from redistribution.
The OSPF network type is broadcast, but the EIGRP redistribution may be causing OSPF LSAs to be flooded with high CPU load, leading to neighbor flapping. Additionally, the hello interval is set to 10 seconds, but the dead interval is not explicitly set, defaulting to 40 seconds. If the router is overloaded, hello packets may be missed. The fix is to increase the dead interval or adjust the network type to point-to-point.
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 interval is too low, causing neighbor flapping under load from redistribution.
Why this is correct
Redistribution increases CPU load, causing hello packets to be delayed and neighbors to time out.
- ✗
The EIGRP metric is misconfigured, causing route inconsistency.
Why it's wrong here
Metric does not affect OSPF neighbor state.
- ✗
The OSPF network type broadcast requires a DR/BDR election, causing instability.
Why it's wrong here
DR/BDR election is stable; the issue is hello timing.
- ✗
The redistribute command under OSPF is missing the metric type.
Why it's wrong here
Missing metric type does not cause neighbor flapping.
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.
Go deeper
Related to this question
About these practice questions
Courseiva writes every 300-410 question from scratch — 1,966 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.