Data-Architect Exam Dumps : Salesforce Certified Platform Data Architect (Plat-Arch-201)

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.

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.

The three characteristics of a Skinny table that help improve report and query performance are: Skinny tables can contain frequently used fields and thereby help avoid joins. Skinny tables are kept in sync with changes to data in the source tables. Skinny tables do not include records that are available in the recycle bin. These characteristics are beneficial because they reduce the query complexity and execution time, and improve the data accuracy and freshness. For example, skinny tables can contain frequently used fields from multiple objects, such as Account and Contact, and thereby help avoid joins that can slow down queries4. Skinny tables are updated automatically when the source tables are modified, so they always reflect the latest data5. Skinny tables do not include records that are available in the recycle bin, so they only contain active records that are relevant for reports and queries.