Salesforce Data-Architect Actual Questions

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.

The three activities that will be required to identify a successful master data management strategy are:

Identify data to be replicated: This activity involves determining which data elements need to be copied from one system to another, and how frequently the replication should occur. This can help ensure data consistency and availability across systems.

Create a data archive strategy: This activity involves defining how historical data will be stored, accessed, and deleted over time. This can help optimize data storage, performance, and compliance.

Define the systems of record for critical data: This activity involves identifying which system owns and maintains the authoritative version of each data element. This can help avoid data conflicts and duplication across systems67.

Install a data warehouse is not a required activity, but rather a possible option for consolidating data from multiple sources for analytics purposes. Choose a Business Intelligence tool is not a required activity, but rather a possible option for visualizing and reporting on data from various sources.

Using an ETL tool to orchestrate the migration is the best strategy for this scenario, as it can handle the data model changes, the large volume of records, and the tight timeline. Writing a script to use the Bulk API (option C) is also possible, but it would require more coding and testing effort. Using Data Loader and Data Import Wizard (option B) is not suitable for migrating three million records, as they have limitations on the batch size and the number of records per operation. Using Salesforce CLI (option D) is also not recommended for large data migration, as it is mainly designed for development and testing purposes

Using external objects to maintain Sales Order in Salesforce is the best recommendation for maintaining Sales Orders in Salesforce, as it allows users to access large volumes of data stored outside Salesforce without copying or synchronizing it. Using custom objects, custom big objects, or standard order object may not be feasible or optimal for storing more than 150 million records that will not be updated in Salesforce.