IPv6 Configuration Scenarios

OSPFv3 authentication configured

Why wrong: Authentication is optional and not required for basic operation.

OSPFv3 LSA type 9 for link-local addresses

Why wrong: LSA type 9 is automatically generated, not a configuration requirement.

TLV 2 (IS Neighbors)

Why wrong: TLV 2 advertises IS-IS neighbors.

TLV 1 (Area Addresses)

Why wrong: TLV 1 advertises area addresses, not prefixes.

TLV 22 (IS Extended Neighbors)

Why wrong: TLV 22 carries neighbor information with extended metrics.

OSPFv3 TE requires the use of wide metrics.

Why wrong: TE metrics can be separate from OSPF cost; wide metrics are not mandatory.

OSPFv3 TE only supports point-to-point links.

Why wrong: OSPFv3 TE supports both broadcast and point-to-point links.

End.X

Why wrong: End.X forwards to a specific neighbor.

End.DT2U

Why wrong: End.DT2U is for L2VPN.

End.DT4

Why wrong: End.DT4 is for IPv4 VPN.

IPv6 prefixes are transported over an IPv6 MPLS core using LDPv6

Why wrong: 6PE assumes the core is IPv4 MPLS.

IPv6 prefixes are encapsulated in IPv4 tunnels with GRE

Why wrong: 6PE does not use GRE; it relies on MPLS and BGP.

IPv6 prefixes are converted to IPv4 using NAT64 before MPLS forwarding

Why wrong: NAT64 is not used in 6PE.

It indicates the length of the SID.

Why wrong: Length is not a part of the SID; it's a separate field.

It encodes an argument for the SRv6 function.

Why wrong: Arguments are in the 'argument' part.

It specifies the function to be performed on the packet.

Why wrong: The function is specified by the 'function' part.

End.DT6

Why wrong: End.DT6 is for IPv6 VPN decapsulation.

End.DT2U

Why wrong: End.DT2U is for L2VPN.

End.DX4

Why wrong: End.DX4 is for L3VPN with cross-connect to a specific interface.

MPLS label switching

Why wrong: MPLS is not specific to MAP-T.

IPv4 in IPv6 encapsulation

Why wrong: MAP-E uses encapsulation; MAP-T uses translation.

IPv6 in IPv4 encapsulation

Why wrong: That is 6rd or 6PE.

Virtual links

Why wrong: Both support virtual links.

Authentication using MD5

Why wrong: OSPFv2 supports MD5; OSPFv3 relies on IPsec.

Route redistribution

Why wrong: Both support redistribution.

NAT64

Why wrong: NAT64 translates between IPv6 and IPv4, does not encapsulate.

MAP-T

Why wrong: MAP-T uses translation, not encapsulation.

OSPFv3 does not support authentication.

Why wrong: OSPFv3 supports authentication via IPsec.

OSPFv3 authenticates using the Authentication field in the OSPF header.

Why wrong: OSPFv3 header has no authentication fields.

OSPFv3 uses the same authentication mechanisms as OSPFv2.

Why wrong: OSPFv2 uses simple password or MD5; OSPFv3 uses IPsec.

IPv6-over-IPv4 tunneling

Why wrong: Tunneling is used in 6to4 or 6rd, not NAT64.

DNS64

Why wrong: DNS64 is used to synthesize AAAA records from A records, but it is not the address translation mechanism itself.

Stateful translation of IPv6 to IPv4 using a pool of IPv4 addresses

Why wrong: Stateful NAT64 does use a pool, but the question asks about address mapping; the mechanism is embedding.

6VPE

Why wrong: 6VPE provides L3VPN for IPv6 with VRF.

NAT64

Why wrong: NAT64 translates IPv6 to IPv4.

MAP-T

Why wrong: MAP-T is for IPv4 over IPv6 encapsulation.

OSPFv3 uses the same LSA types as OSPFv2.

Why wrong: OSPFv3 has modified LSA types (e.g., Link LSA, Intra-Area Prefix LSA).

OSPFv3 requires both IPv4 and IPv6 addresses on interfaces.

Why wrong: OSPFv3 is for IPv6 only; no IPv4 needed.

OSPFv3 uses IPv6 addresses to form adjacencies.

Why wrong: Adjacencies are formed using Router IDs and link-local addresses are used for packets.

Labeled unicast IPv4 address family

Why wrong: Not used for 6PE.

VPNv4 address family with route-target extended community

Why wrong: That's for MPLS L3VPN.

IPv6 address family with next-hop encoded as an IPv6 address

Why wrong: 6PE uses IPv4 next-hop.