Refer to the exhibit.

In PIM Sparse Mode, when the Last-Hop Router (LHR) receives multicast traffic on the shared tree (*,G), it performs an RPF check based on the RP address, not the multicast source address. In the diagram:

The LHR has IGP cost 10 towards the RP.

The shared tree (*,G) uses RP as the RPF target.

Since multicast traffic on (*,G) arrives on the interface toward RP (correct RPF interface), the RPF check succeeds.

Therefore, the multicast traffic is successfully switched toward the receivers.

This behavior is fully aligned with CCDE v3.1 multicast design principles, which emphasize clear understanding of RPF behavior both on shared trees (*,G) and source trees (S,G).

Why other options are incorrect:

A: The RPF check is not performed against the source in (*,G); it uses RP.

B: RPF checks are always performed, even on (*,G).

D: RPF is unrelated to the receiver address.