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.

Creating an account plan object with a lookup relationship to Account with validation rules to enforce the Account association can help UC meet their requirement. A lookup relationship allows different accessibility requirements for the account plan object and the account object, as well as different ownership and sharing settings. A validation rule can ensure that each account plan has an account associated with it.

According to Trailhead2, Salesforce Connect is a feature that allows administrators to integrate external data sources with Salesforce without copying or synchronizing the data. Salesforce Connect can use external objects to display the external data in Salesforce as if it were stored in Salesforce objects, enabling seamless user experience and real-time access. Option B is the correct answer because it suggests using Salesforce Connect and an external object to display the order history in Salesforce. Option A is incorrect because using an Apex callout to populate a text area field for displaying the order history can be inefficient and unreliable, as it requires making an HTTP request for each customer record and storing the order history as unstructured text. Option C is incorrect because importing the order history into a custom Salesforce object, update nightly can consume a lot of storage space and cause data latency, as the order history may change more frequently than once a night. Option D is incorrect because embedding the ERP system in an iframe and displaying on a custom tab can degrade the user experience and security, as it requires switching between tabs and authenticating with another system.