A water utility wants high-rate camera groups to use one RP and low-rate SCADA sensor groups to use another so shared-tree load is engineered separately. What configuration concept enables that separation?
Select an answer to reveal the explanation.
Short Explanation
Think of two ticket windows: cameras queue at RP-A, sensors at RP-B. Group-to-RP maps (ACLs or candidate-RP scopes) send each range to the right window so one busy tree doesn’t crush the other. Same PIM-SM idea—just smarter who sits at the hub.
Full Explanation
PIM-SM allows different RPs to serve different multicast group ranges through static RP ACLs, Auto-RP scoped announcements, or BSR candidate-RP group lists. Mapping high-bandwidth groups to one RP and sparse sensor groups to another engineers shared-tree and Register load independently. Omitting mapping (or collapsing everything to one RP without policy) forgoes that traffic-engineering lever.