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

 Using hard delete in Bulk API, identifying records that have not been modified or used in last 3 years, and archiving the records in EDW before deleting from Salesforce are all good recommendations to reduce the number of records from the org1. Using hard delete in batch Apex or Rest API may not be as efficient or scalable as Bulk API

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.

Data Loader uses external Id fields to match records in the CSV file with records in Salesforce during an upsert operation. If the CSV file contains duplicate external Id values within the same file, Data Loader will throw an error saying “Duplicate Id Specified” and will not process those records. Therefore, it is important to ensure that the CSV file does not have any duplicate external Id values before using Data Loader to upsert records.