Table of Contents
Question
Universal Containers uses multiple Salesforce orgs for its different lines of business (LOBs). In a recent analysis, the architect found that UC could have a more complete view of its customers by gathering customer data from different orgs. What two options can an architect recommend to accomplish the customer 380-degree view? (Choose two.)
A. Implement a Complete Graph multi-org strategy by allowing each org to connect directly to every other, reading and writing customer data from the orgs where it has been originally created.
B. Migrate from multi-org to single-org strategy, consolidating customer data in the process.
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.
Answer
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.
Explanation
To accomplish a 360-degree view of customers by gathering customer data from different Salesforce orgs, an architect can recommend the following two options:
C. Implement a Single Package multi-org strategy by developing and deploying a managed package that reads and consolidates the customer 360-degree view from the different orgs.
With this approach, the architect can develop a managed package that can be deployed to all the orgs. The managed package would contain the necessary components, such as custom objects, fields, and logic, to extract and consolidate customer data from each org into a unified view. This strategy allows for data aggregation and provides a comprehensive view of the customers across the multiple 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.
In this approach, the architect can designate one Salesforce org as the “hub” or central org that acts as the master of customer data. The customer data from different LOB orgs can be consolidated into the central org, enabling a complete view of customers. Integration strategies, such as APIs or middleware, can be used to establish communication between the LOB orgs and the central org, allowing the LOB orgs to read and write customer data as needed.
Both options C and D aim to consolidate customer data from multiple orgs to provide a more complete view of customers. Option C utilizes a managed package approach to achieve data consolidation, while option D focuses on a centralized “hub-and-spoke” model for data management.
It’s important to consider the specific requirements, data volume, data privacy, and governance needs of Universal Containers when choosing the most suitable approach. Additionally, thorough planning and analysis are necessary to ensure successful implementation and seamless integration of customer data across the different orgs.
Reference
- What is a 360-Degree View of a Customer?| SitecoreBlog
- 6 Best Practices For Creating A Container Platform Strategy (gartner.com)
Salesforce Certified Development Lifecycle and Deployment Architect certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Salesforce Certified Development Lifecycle and Deployment Architect exam and earn Salesforce Certified Development Lifecycle and Deployment Architect certification.