Question 630
At an enterprise telemetry network with multicast subscribers, a Junos specialist investigates this scenario: A conferencing application expects an unknown multicast source but engineers require each client to specify a sender IP. The team should test joins and forwarding separately. Which limitation should guide the change control?
Explanation
Correct Answer
For an enterprise telemetry network with multicast subscribers, the relevant safeguard is: Consider unwanted sources and multicast boundary controls in an open ASM group. It matters while implementing: Design a suitable ASM group with functioning IGMP membership and rendezvous-point information. The fault involves: Any-source multicast allows receivers to request a group independent of a specific source, typically using a shared-tree mechanism. The required acceptance result remains: A receiver can join G and obtain traffic from an approved discovered sender.
Incorrect Answers
Shared-tree (*,G) state expresses interest in traffic to group G from potentially multiple sources. The appropriate correction for the reported case is: Consider unwanted sources and multicast boundary controls in an open ASM group.
PIM routers discover routing neighbors on participating interfaces through PIM Hello exchanges. Fixing that different mechanism would not address the current root cause: any-source multicast allows receivers to request a group independent of a specific source, typically using a shared-tree mechanism.
PIM sparse mode builds multicast forwarding paths in response to explicit joins rather than flooding everywhere. Its verification is distinct from the reported condition: A conferencing application expects an unknown multicast source but engineers require each client to specify a sender IP. The team should test joins and forwarding separately.