When multicast is included in a Cisco SD-Access architecture, the architect must account for multicast transport in the overlay for endpoint traffic. Cisco SD-Access separates the underlay, which provides IP connectivity between fabric nodes, from the overlay, which carries user endpoint traffic in the endpoint identifier space. For wired and wireless clients, multicast traffic is transported as part of the overlay service rather than treating clients as underlay participants. That is why the correct design element is that multicast traffic is transported in the overlay and EID space for both wired and wireless clients. PIM SSM does not have to run in the underlay for this purpose, and multicast clients do not simply reside in the underlay. The statement about RPs being required in an SSM deployment is also wrong because source-specific multicast is specifically designed to avoid the traditional RP model. In a fabric design, multicast requirements affect border behavior, receiver placement, replication mode, wireless integration, and policy boundaries. Reference topics: Cisco SD-Access multicast, overlay forwarding, EID space, wired and wireless fabric clients.