A museums and culture department needs many sensors to talk to many collectors on the same groups without building a separate (S,G) tree per sender. Which PIM variant is designed for that many-to-many pattern?
Select an answer to reveal the explanation.
Short Explanation
When dozens of sensors all jabber on one group, building a shortest-path tree for every source turns into a state avalanche. Bidirectional PIM keeps traffic on shared trees both ways toward the RP, so you skip that per-source tree tax. It’s the many-to-many specialist.
Full Explanation
Bidirectional PIM (Bidir-PIM) forwards multicast on shared trees rooted at an RP (with a designated forwarder election on each link) and does not switch to source-specific (S,G) trees. That design avoids the control-plane and mroute-state growth typical when many sources share groups under classic PIM-SM SPT behavior. SSM and dense-mode models do not address this many-to-many shared-tree efficiency goal.