Most Recent Salesforce Data-Architect Exam Questions & Answers

The correct answer is A. To provide additional guidance for users when they enter information in a standard field, a data architect should provide custom help text under field properties. This will display a help icon next to the field label that users can hover over to see the help text. Option B is incorrect because creating a custom page with help text for user guidance will require additional development effort and may not be easily accessible by users. Option C is incorrect because adding custom help text in default value for the field will overwrite the actual default value of the field and may confuse users. Option D is incorrect because adding a label field with help text adjacent to the custom field will clutter the page layout and may not be visible to users.

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.

The correct answer is C, migrate Notes and Attachment to Enhanced Notes and Files using a migration tool. Enhanced Notes and Files are the new features in Lightning Experience that replace the classic Notes and Attachments. They offer more functionality and security than the classic version. To access them in Lightning Experience, you need to migrate your existing Notes and Attachments using a migration tool provided by Salesforce. Adding Notes and Attachments Related List, manually uploading Notes or Attachments, or doing nothing are not valid solutions, as they will not enable you to use the enhanced features in Lightning Experience.

Integrating Salesforce with ERP and making ERP the system of truth (option B) and implementing a de-dupe solution and establishing account ownership in Salesforce (option D) are the two solutions that a data architect should recommend to resolve the complaints. Option B ensures that account data is consistent and accurate across both systems, while option D prevents duplicate records and clarifies who owns each account in Salesforce. Building a nightly batch job to de-dupe data and merge account records (option A) is not a good solution, as it does not address the root cause of the duplication and may result in data loss or conflicts. Building a nightly sync job from ERP to Salesforce (option C) is also not sufficient, as it does not prevent duplication or establish ownership in Salesforce.

Option D is correct because data flows should be reviewed with the business users to determine the system of record per object or field1.The system of record is the authoritative source of data for a given entity or attribute2. It may vary depending on the business context and requirements.Option A is not correct because account and opportunity data originates in Salesforce, but it may not be the system of record for all attributes or objects if they are updated by other systems2.Option B is not correct because whatever system updates the attribute or object may not be the system of record for that field or object if there are conflicting or overlapping updates from other systems2.Option C is not correct because whatever integration data flow runs last may not determine which system is the system of record if there are different business rules or logic applied by different systems2.