OSPFv3 uses the same route advertisement method as OSPFv2; it is advertised through the network command in the OSPFv3 area view.

Question

Options

• ATRUE
• BFALSE

• A
  27% (6)
• B
  73% (16)

Explanation

B is correct because OSPFv3 does not use the network command to advertise routes. Unlike OSPFv2, where you define which networks participate in OSPF at the process level using network <address> <wildcard> area <id>, OSPFv3 is enabled directly on individual interfaces using an interface-level command (e.g., ospf <process-id> area <area-id> applied per interface). This is a fundamental architectural difference introduced with OSPFv3 to support IPv6.

Why A is wrong: The statement claims OSPFv3 mirrors OSPFv2's advertisement method - this is false because the two versions use entirely different mechanisms for bringing interfaces into the OSPF process. Assuming IPv6 protocols simply replicate IPv4 behavior is a common trap.

Memory tip: Associate "v3" with "interface-level" - OSPFv3 dropped the centralized network command and moved responsibility down to each interface. If you remember "v3 = per-interface opt-in," you'll never confuse the two on an exam.

No community discussion yet for this question.