352-001 · Question #455
What is a correct design consideration of IPv6 MLD snooping?
The correct answer is D. MLD snooping conserves bandwidth on switches. MLD snooping is the IPv6 equivalent of IGMP snooping and conserves bandwidth by forwarding multicast traffic only to ports with interested listeners rather than flooding all ports.
Question
What is a correct design consideration of IPv6 MLD snooping?
Options
- AMLD snooping requires IGMP snooping to be implemented.
- BMLD snooping conserves CPU by sharing IPv4 and IPv6 multicast topology.
- CMLD snooping is used to filter all MLD queries.
- DMLD snooping conserves bandwidth on switches.
How the community answered
(33 responses)- A3% (1)
- B6% (2)
- D91% (30)
Why each option
MLD snooping is the IPv6 equivalent of IGMP snooping and conserves bandwidth by forwarding multicast traffic only to ports with interested listeners rather than flooding all ports.
MLD snooping is an independent IPv6 mechanism and does not require IGMP snooping, which is a separate IPv4-only feature.
MLD snooping and IGMP snooping maintain completely separate multicast membership tables - there is no shared IPv4/IPv6 multicast topology between them.
MLD snooping does not filter MLD queries; it listens to MLD messages to populate its membership table and forwards queries to build group membership.
MLD snooping works by listening to MLD membership reports exchanged between IPv6 hosts and multicast routers, allowing the switch to build a port membership table. This enables the switch to forward multicast streams only to ports with active listeners, preventing unnecessary flooding across all switch ports and conserving bandwidth.
Concept tested: IPv6 MLD snooping bandwidth conservation on switches
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipmulti_lsm/configuration/xe-16/imc-lsm-xe-16-book/ipv6-mld-snooping.html
Topics
Community Discussion
No community discussion yet for this question.