A city public-works team must keep administratively scoped site-local multicast groups from being forwarded onto the WAN. Which mechanism directly enforces that containment?
Select an answer to reveal the explanation.
Short Explanation
Scoped groups are the “employees only” hallway—fine inside the building, not across the city WAN. A multicast boundary on the WAN edge is the door lock that drops those ranges before they leak. Without it, site-local chatter rides outbound like any other group.
Full Explanation
Administratively scoped multicast ranges (for example 239.0.0.0/8 usage policies) are contained by configuring multicast boundaries or equivalent filters on interfaces that should not forward those groups. The boundary prevents both data-plane leakage and often unwanted control-plane join propagation for filtered groups. Adjusting IGP metrics, disabling snooping, or changing PIM dense/sparse mode does not substitute for explicit group scoping at the site edge.