Refer to the exhibit. As part of a redesign project, you must predict multicast behavior. What is the resultant multicast traffic receiving on the shared tree( , G), if it is received on the LHR…

RPF checks in multicast routing are never performed against the multicast receiver - receivers are downstream and do not factor into RPF logic.

For shared tree (*, G) entries, the RPF check is performed against the unicast routing table to find the best path toward the Rendezvous Point (RP), not the source. If the multicast packet arrives on the interface that the router would use to reach the RP, the RPF check succeeds and the traffic is switched downstream. This is the standard PIM-SM behavior for shared tree forwarding on the LHR.

An RPF check is always performed on multicast traffic, including shared tree (*, G) entries; there is no scenario where multicast forwarding skips the RPF check entirely.

Checking RPF against the multicast source applies to source-specific (S, G) entries, not shared tree (*, G) entries, where the RPF lookup targets the RP address instead.