B. Put customer data in Global: This is incorrect as it violates the core principle of domain separation, which is to segregate customer data. Global data is visible to all users in all domains.
C. No action required: This is only true if a specific parent-child domain hierarchy is already established where the SP is in the parent domain. It is not a universally applicable practice "to allow" visibility, as action is required if this structure is not in place.
D. Setup a visibility group: While visibility groups also grant cross-domain access, they are typically used for specific sets of users or roles. A 'contains' relationship is a broader, domain-to-domain rule, making it more suitable for granting visibility to the entire SP organization.