Plat-Arch-201 practice question 3 of 10

Universal Containers (UC) has multi -level account hierarchies that represent departments within their major Accounts. Users are creating duplicate Contacts across multiple departments. UC wants to clean the data so as to have a single Contact across departments. What two solutions should UC implement to cleanse their data? Choose 2 answers

Full set: 257 questions
Answer options
A: Make use of a third -party tool to help merge duplicate Contacts across Accounts. Correct answer
B: Use Data.com to standardize Contact address information to help identify duplicates. Correct answer
C: Use Workflow rules to standardize Contact information to identify and prevent duplicates.
D: Make use of the Merge Contacts feature of Salesforce to merge duplicates for an Account.
Correct Answer:
A. Make use of a third -party tool to help merge duplicate Contacts across Accounts.; B. Use Data.com to standardize Contact address information to help identify duplicates.
Explanation

Salesforce’s native Merge Contacts only merges records that share the same Account. Because UC needs one Contact shared by several departments (different Accounts), they must (1) use a tool that can merge across-account duplicates, and (2) improve matching accuracy by standardizing key fields such as address. Data.com Clean provides postal-address standardization that makes cross-account duplicate detection far more reliable.

Why Incorrect

C. Workflow/field updates can’t parse, cleanse, or compare multi-account records; duplicates would still exist.
D. Native Merge Contacts is limited to Contacts under a single Account, so cross-account duplicates remain.

References

1. Salesforce Help “Merge Duplicate Contacts in Lightning Experience”, Limitations section, DOC-ID: 000334409.

2. Salesforce Help “Data.com Clean: How Address Standardization Works”, Address Standardization subsection.

3. Trailhead Module “Improve Your Data Quality”, Unit: Prevent and Merge Duplicate Data.

Scroll to Top