mediumMultiple Choice
CCNP Practice Question: Examine the following configuration snippet:…
Examine the following configuration snippet:
interface GigabitEthernet0/1 ip address 192.168.1.1 255.255.255.0 ip ospf hello-interval 20 ip ospf dead-interval 80
What is the effect of this configuration?
⚠ Common exam trap
Cisco often tests the misconception that the dead interval must always be exactly 4 times the hello interval, but the actual requirement is that the timers must match between neighbors, not that a specific ratio must be maintained.
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 changed to 20 seconds, and the dead interval is changed to 80 seconds, maintaining the default 4:1 ratio.
The configuration explicitly sets the OSPF hello interval to 20 seconds and the dead interval to 80 seconds, which maintains the default 4:1 ratio (dead = hello × 4). OSPF allows manual configuration of these timers, and as long as both sides of the adjacency match, the ratio can be any value; the 4:1 default is not enforced by the protocol.
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 changed to 20 seconds, and the dead interval is changed to 80 seconds, maintaining the default 4:1 ratio.
Why this is correct
The OSPF configuration in the scenario explicitly sets the hello interval to 20 seconds and the dead interval to 80 seconds, which preserves OSPF's default dead-to-hello ratio of 4:1 (80/20 = 4). Because both neighbors are configured with these same values, the OSPF dead interval timer remains consistent, and adjacency formation occurs normally. This matches the requirement that neighbors must agree on timer values, not that a strict 4:1 ratio is mandated.
- ✗
The OSPF hello interval is changed to 20 seconds, but the dead interval remains at the default of 40 seconds.
Why it's wrong here
This option incorrectly claims the dead interval stays at the default 40 seconds after the hello interval is changed to 20 seconds. In the given configuration, the dead interval is explicitly overridden to 80 seconds, so the final value is not 40. Even if the dead interval were 20 seconds (a 1:1 ratio) or 40 seconds (2:1), OSPF would still permit adjacency provided both sides advertise identical timers, but that is not what the configuration does.
- ✗
The OSPF hello interval is changed to 20 seconds, and the dead interval is automatically set to 60 seconds.
Why it's wrong here
This option asserts that the dead interval is automatically recalculated to 60 seconds when the hello interval is set to 20 seconds. OSPF does not dynamically derive the dead interval from the hello interval; the dead interval is an independent timer that must be manually configured. In the scenario, the dead interval is explicitly set to 80 seconds, not auto-computed to 60, so this choice misstates both the configuration and OSPF behavior.
- ✗
This configuration will cause OSPF adjacency failure because the dead interval must be exactly 4 times the hello interval.
Why it's wrong here
This option incorrectly predicts an adjacency failure because it assumes OSPF mandates a dead interval of exactly four times the hello interval. In reality, OSPF only requires routers on the same link to have matching hello and dead intervals; the 4:1 ratio is merely the default, not a protocol constraint. Since the configuration sets both timers to 20 and 80 seconds, the timers agree across the link, so adjacency forms successfully.
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 writes every 350-401 question from scratch — 1,923 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 350-401 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 350-401 exam.