Salesforce Developer Development-Lifecycle-and-Deployment-Architect Question # 2 Topic 1 Discussion

Deploying metadata to production orgs using package development model is the best option for the multi-org deployment strategy, as it allows you to create modular and reusable packages that can be easily installed and updated across different orgs. Deploying metadata to production orgs using managed packages is not suitable for this scenario, as managed packages are typically used by ISVs to distribute their applications to customers, and they have some limitations and restrictions that may not fit the requirements of UC. Deploying metadata to production orgs using unmanaged packages is also not a good option, as unmanaged packages are mainly used for one-time distribution of components, and they do not support upgrades or dependencies. Deploying metadata to production orgs using change sets is not feasible for this scenario, as change sets can only be used to deploy metadata between connected orgs in the same Salesforce instance, and UC has separate orgs for each region. See [Package Development Model] for more details.