Salesforce Data-Architect Exam With Confidence Using Practice Dumps

Creating a report in an external system combining Salesforce Account data and Invoice data from the ERP, and creating a Visualforce page combining Salesforce Account data and Invoice external object data are two approaches that an architect can suggest for achieving this solution. Both of these approaches can display data from both Accounts and Invoices in one place, using either an external reporting tool or a custom web page. Creating a report combining data from the Account standard object and the Invoices external object is not possible because Salesforce does not support reporting on external objects. Creating a separate Salesforce report for Accounts and Invoices and combining them in a dashboard is not ideal because it will not show the data in one report, but rather in two separate components.

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.

Data skew occurs when a large number of child records are associated with a single parent record, or when a single user owns a large number of records. This can cause performance issues and lock contention. To avoid data skew, the data architect should limit assigning one user 10,000 records ownership, limit associating 10,000 opportunities to one account, and limit associating 10,000 records looking up to the same record