Universal Containers uses multiple Salesforce orgs for its different lines of business (LOBS).

The correct selection is C, D. A multi-org Customer 360 strategy should avoid uncontrolled point-to-point connectivity. A reusable package can standardize common customer-view functionality across orgs, while a hub-and-spoke pattern centralizes authoritative customer data and lets business-unit orgs integrate to that master. From a system-design perspective, the decision should minimize unnecessary coupling while preserving clear ownership, scalability, governance, and extensibility. Salesforce architecture is strongest when boundaries reflect real business and technical responsibilities instead of using organizational convenience as the primary design driver. The rejected designs either centralize too much, fragment without justification, or use a mechanism that does not create the required architectural contract between systems or teams. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (C. Implement a Single Package multi-org strategy by developing and deploying to all orgs a managed package which reads and consolidates customer 360-degree view from the different orgs.; D. Implement a Hub-and-Spoke multi-org strategy by consolidating customer data in a single org, which will be the master of customer data, and using integration strategies to let the LOBS orgs read and write from it.). Applying that rule consistently keeps the implementation aligned with Salesforce-supported lifecycle practices and makes the resulting change easier to review, validate, and operate across environments.

Study Guide reference: System Design — org strategy; modular architecture; integration topology; data ownership; enterprise governance; scalability.