What is a correct design consideration of IPv6 MLD snooping?

Question

Options

• AMLD snooping conserves bandwidth on switches.
• BMLD snooping is used to filter all MLD queries.
• CMLD snooping requires IGMP snooping to be implemented.
• DMLD snooping conserves CPU by sharing IPv4 and IPv6 multicast topology.

• A
  94% (49)
• B
  2% (1)
• C
  4% (2)

Explanation

MLD (Multicast Listener Discovery) snooping allows a switch to inspect MLD messages exchanged between IPv6 hosts and routers, enabling it to forward multicast traffic only to ports with interested receivers rather than flooding it to all ports - this is exactly why A is correct: it conserves bandwidth.

B is wrong because MLD snooping doesn't filter all MLD queries - it actually needs to pass queries through to function correctly. Blocking all queries would break multicast group discovery entirely.

C is wrong because MLD snooping is independent of IGMP snooping. MLD is the IPv6 equivalent of IGMP (IPv4), but they operate as separate protocols on separate stacks - no dependency exists between them.

D is wrong because IPv4 and IPv6 maintain completely separate multicast topologies. MLD snooping builds an IPv6-specific table; it does not share or reduce CPU by merging it with IPv4 IGMP state.

Memory tip: Think of "snooping" as eavesdropping - the switch listens in on MLD conversations to learn who wants what multicast traffic, then delivers it only where needed. Less flooding = less wasted bandwidth. That's the whole point.

No community discussion yet for this question.