Question 799 of 1,389
CCNA IP Routing Practice Question
Which TWO statements accurately describe OSPFv3 configuration and verification for IPv6?
⚠ Common exam trap
Cisco often tests the misconception that OSPFv3 uses the same 'network' command as OSPFv2, when in fact OSPFv3 requires interface-level configuration with the 'ipv6 ospf <process-id> area <area-id>' command.
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
✓
OSPFv3 uses IPv6 link-local addresses for neighbor discovery and next-hop addresses.
OSPFv3 uses IPv6 link-local addresses for neighbor discovery and next-hop addresses. Option C is correct because the 'ipv6 ospf <process-id> area <area-id>' interface command enables OSPFv3 on that interface. Option B is incorrect: OSPFv3 does not use the 'network' command; instead, it relies on interface-level configuration. Option D is incorrect: 'ipv6 router ospf <process-id>' is a global configuration command to enter OSPFv3 router configuration mode, not an interface command. Option E is incorrect: 'show ipv6 ospf neighbor' displays neighbor adjacencies, not the link-state database; use 'show ipv6 ospf database' for that.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
OSPFv3 uses IPv6 link-local addresses for neighbor discovery and next-hop addresses.
Why this is correct
OSPFv3 routers build neighbor adjacencies and exchange hello packets using their IPv6 link-local addresses, so those addresses appear as the neighbor address and as the next hop for routes learned from that neighbor. On point-to-point and broadcast links, the link-local address is always used for forwarding to an adjacent router, even if global unicast addresses are also configured on the interface. This design lets OSPFv3 operate without depending on IPv4-mapped global addresses and avoids renumbering issues.
- ✗
The 'network' command under 'ipv6 router ospf' is used to advertise subnets into OSPFv3.
Why it's wrong here
In OSPFv3, the IPv6 address-family implementation does not support the IPv4-style 'network' statement under 'ipv6 router ospf' to select interfaces or advertise subnets. OSPFv3 relies on interface-level activation with 'ipv6 ospf <process-id> area <area-id>', which associates each interface directly with a process and area. The 'network' command is a legacy OSPFv2 mechanism that matches IPv4 prefixes; it has no equivalent in OSPFv3 because IPv6 interfaces are enabled explicitly on the interface itself.
- ✓
The 'ipv6 ospf <process-id> area <area-id>' command is used to enable OSPFv3 on an interface.
Why this is correct
On an interface, the command 'ipv6 ospf <process-id> area <area-id>' enables OSPFv3 for that interface and places it in a specified area, replacing the need for a network statement. This interface-specific configuration is mandatory in OSPFv3; OSPFv3 does not automatically advertise an IPv6 subnet unless it is active on an interface where this command is applied. The process-id must already exist or be created by 'ipv6 router ospf <process-id>'.
- ✗
The 'ipv6 router ospf <process-id>' command is used on an interface to enable OSPFv3.
Why it's wrong here
The command 'ipv6 router ospf <process-id>' executed in global configuration mode creates or enters the OSPFv3 routing process, not an interface. It is only used to configure router-level settings such as router-id, timers, and redistributions. To enable OSPFv3 on a specific interface, you must enter interface configuration mode and issue 'ipv6 ospf <process-id> area <area-id>'.
- ✗
The 'show ipv6 ospf neighbor' command displays the OSPFv3 link-state database.
Why it's wrong here
The 'show ipv6 ospf neighbor' command displays only OSPFv3 neighbor adjacencies: neighbor ID, priority, state, dead time, and link-local interface address. It does not show the link-state database. The OSPFv3 LSDB, with LSA headers and details, is displayed using 'show ipv6 ospf database' or 'show ipv6 ospf database [router | network | inter-prefix | inter-router | ... ]'.
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.
✓OSPFv3 uses IPv6 link-local addresses for neighbor discovery and next-hop addresses.Correct answer▾
Why this is correct
OSPFv3 routers build neighbor adjacencies and exchange hello packets using their IPv6 link-local addresses, so those addresses appear as the neighbor address and as the next hop for routes learned from that neighbor. On point-to-point and broadcast links, the link-local address is always used for forwarding to an adjacent router, even if global unicast addresses are also configured on the interface. This design lets OSPFv3 operate without depending on IPv4-mapped global addresses and avoids renumbering issues.
✗The 'network' command under 'ipv6 router ospf' is used to advertise subnets into OSPFv3.Wrong answer — click to see why▾
Why this is wrong here
OSPFv3 does not use the 'network' command; instead, it is enabled directly on interfaces using the 'ipv6 ospf <process-id> area <area-id>' command. The 'network' command is used in OSPFv2 for IPv4.
Why candidates choose this
Students familiar with OSPFv2 may mistakenly think the 'network' command also applies to OSPFv3, but OSPFv3 uses a different configuration model.
✗The 'ipv6 router ospf <process-id>' command is used on an interface to enable OSPFv3.Wrong answer — click to see why▾
Why this is wrong here
The 'ipv6 router ospf <process-id>' command is a global configuration command that enters OSPFv3 router configuration mode, not an interface command. It does not enable OSPFv3 on an interface.
Why candidates choose this
The command name includes 'router ospf', which might lead students to think it is used on interfaces, but it is actually a global command.
✗The 'show ipv6 ospf neighbor' command displays the OSPFv3 link-state database.Wrong answer — click to see why▾
Why this is wrong here
The 'show ipv6 ospf neighbor' command displays OSPFv3 neighbor states and adjacencies, not the link-state database. The LSDB is shown with 'show ipv6 ospf database'.
Why candidates choose this
Students may confuse 'neighbor' with 'database' because both are OSPF show commands, but they serve different purposes.
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?”
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 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 →
Last reviewed: Jun 11, 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.