Salesforce Certified Data Architect Practice Test - Questions Answers, Page 21

Enabling granular locking allows concurrent sharing rule calculations and group membership updates to run without locking each other1. This can help resolve the group membership locking issues that UC is experiencing.

Ensuring the lead data is preprocessed for quality before loading into Salesforce is the best way to maintain data quality2. Activating validation rules after the load or developing a custom Apex batch process may not catch all the errors or may require additional time and resources. Allowing validation rules to be activated during the load may cause failures or delays.

Leveraging Heroku Connect and Heroku Postgres, middleware tools, or Salesforce Connect and the cross-org adapter are all viable options to share data between Org A and Org B in near-real time3. Installing a 3rd party AppExchange tool may not provide bidirectional sync or may have additional costs. Developing an Apex class that pushes opportunity data between orgs daily via the Apex schedule may not meet the near-real time requirement.

Lightning Platform Plus is the license type that best fits UC's requirements, as it allows up to 50 custom objects and 40,000 API calls per user per 24-hour period4. Service Cloud does not provide enough custom objects or API calls. Lightning Platform Start only allows up to 10 custom objects and 5,000 API calls per user per 24-hour period. Lightning External Apps Start is for external users and does not provide enough API calls.

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

Exploring external data sources in Salesforce to build 360 view of customer is the best strategy to satisfy the requirement, as it allows real-time access to data from other systems without storing it in Salesforce3. Using a customer data mart may not provide real-time information or may require additional integration efforts. Migrating customer activities from all 4 systems into Salesforce may exceed the storage limits or cause data quality issues. Periodically uploading summary information in Salesforce may not provide current or detailed information.

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.

Ensuring validation rules, triggers and other automation tools are disabled is the best way to mitigate any unwanted results during the import, as it prevents any errors or conflicts that may occur due to the existing logic. Ensuring duplication and matching rules are defined may not be sufficient or relevant for preventing unwanted results. Importing the data in smaller batches over a 24-hour period may not be necessary or efficient. Bulkifying the trigger to handle import leads may not be possible or desirable if the triggers were not designed to run during a data load.

Using a validation rule is the best way to ensure that all customers provide either a phone number or an email address when registering for an account, as it allows defining a formula that evaluates whether a record meets certain criteria. Using required fields may not work if both phone number and email address are required. Using an Apex class or a Process Builder may be more complex or cumbersome than using a validation rule.