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

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.

When denormalizing a data model into a single object with a picklist field, the data architect should consider the Bulk API limitations on picklist fields and the standard list view in-line editing. The Bulk API has a limit of 1,000 distinct picklist values per file1, which could be an issue if there are more than 1,000 venues in the future. The standard list view in-line editing allows users to edit multiple records at once, which could introduce data quality issues if the venue picklist is not validated or restricted2. The other options are not relevant to denormalizing a data model.

The two features that a data architect should recommend to share records between Salesforce orgs are:

Change Data Capture (CDC): This is a feature that publishes change events for changes in Salesforce records, such as create, update, delete, and undelete operations. Change events can be subscribed by external systems or other Salesforce orgs using various tools, such as Platform Events, Streaming API, or CometD. CDC can help keep data in sync between Salesforce orgs in near real time89.

Salesforce to Salesforce (S2S): This is a feature that allows sharing records and related data with other Salesforce orgs that you partner with. You can choose which records and fields to share, and which orgs to share with. You can also accept updates from the other orgs to keep the data consistent10.

Salesforce Connect is not a good feature to share records between Salesforce orgs because it is intended for integrating external data sources with Salesforce using external objects. Federation Search is not a good feature to share records between Salesforce orgs because it is intended for searching across multiple Salesforce orgs without sharing data.