Pass Development-Lifecycle-and-Deployment-Architect Exam Guide

 The Metadata API is mainly used for file-based deployment, such as deploying an application from a Developer Edition org to the AppExchange, or from a sandbox org to a production org. The Ant Migration Tool is a wrapper around the Metadata API, so it is not a direct use case for writing code to call retrieve() and deploy() methods. The Salesforce CLI (SFDX) uses the Source-Driven Development model, which relies on the source code as the source of truth, rather than the Metadata API.

Implementing 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 is one of the options an architect can recommend to accomplish the customer 360-degree view. This way, the architect can ensure that there is a single source of truth for the customer data, and that the data is consistent and synchronized across the different orgs. Implementing 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 is another option an architect can recommend, as it allows the architect to create a reusable and scalable solution that can provide a unified view of the customer data from multiple sources. Implementing a Complete Graph multi-org strategy or migrating from multi-org to single-org strategy are not feasible or optimal options, as they can introduce complexity, cost, or risk to the architecture.

C is the correct answer, as creating a custom metadata type and including this in your deployment to production is the best way to manage this deployment. A custom metadata type is a metadata component that can store important configuration data, such as custom settings, and can be deployed along with other components, such as Apex classes. A is incorrect, as scripting the deployment of all functionality via the Force.com Migration Tool is not a good way to manage this deployment, as it does not address the issue of deploying the custom settings that hold the configuration data. B is incorrect, as manually deploying and populating custom settings in production using a change set is not a good way to manage this deployment, as it can introduce errors and inconsistencies, as well as require additional steps and permissions. D is incorrect, as manually deploying and populating the custom settings in production prior to the Apex class deployment is not a good way to manage this deployment, as it can create dependency and timing issues, as well as require additional steps and permissions. You can learn more about this topic in the [Custom Metadata Types] module on Trailhead.

A single-org strategy is the best option for UC, as it will enable them to achieve business process standardization among all business units, which is the main goal of the CEO. A multi-org strategy would make it harder to enforce consistent processes and policies across the different business units, and would also increase the costs and complexity of managing multiple orgs. A common managed package could help with some aspects of standardization, but it would not cover all the possible scenarios and customizations that UC might need.