Salesforce Data-Architect Exam With Confidence Using Practice Dumps

Creating a unique global customer ID for each customer and storing that in all systems for referential identity (option A), investing in a data duplicate tool to de-dupe and merge duplicate records across all systems (option C), and creating a customer master database external to Salesforce as a system of truth and syncing the customer data with all systems (option E) are the three options that a data architect should perform to resolve the issues with the customer data. Option A ensures that each customer can be uniquely identified across different systems, option C eliminates duplicate records and improves data quality, and option E provides a consistent and reliable source of customer data for all systems. Using Salesforce CDC to sync customer data across all systems (option B) is not a good option, as it does not address the duplication or inconsistency issues. Duplicating customer records across the system and providing a two-way sync of data between the systems (option D) is also not a good option, as it may create more confusion and conflicts with customer data.

Option B is the most appropriate approach for data archiving in this scenario1. By aggregating order amount data at a summary level and storing it in a custom object, you can reduce data storage and still provide visibility to the Sales Reps on how much money each customer generates year-over-year. Option A is not correct because storing data in a zip file does not make it available in Salesforce. Option C is not correct because exporting and deleting orders and order line items may lose important details that are needed for analysis or reporting. Option D is not correct because deleting orders and order line items without exporting them may cause data loss or inconsistency if the customer does not have order information in another system.

Implementing a workflow rule that sends Opportunity data through Outbound Messaging is the optimal real-time approach that achieves the solution of copying Opportunity records to the ERP once they reach a Closed/Won Stage. A workflow rule can trigger an Outbound Message when an Opportunity record meets certain criteria, such as having a Closed/Won Stage. An Outbound Message can send data from Salesforce to an external system via SOAP API, without requiring any code. The external system can then process the data and create a read-only record in the ERP system. The other options are not optimal or real-time, as they would either require additional systems or tools, not provide real-time data synchronization, or not meet the frequency requirement