MENU
A large automobile company has implemented Salesforce for its sales associates. Leads flow from its website to Salesforce using a batch integration in Salesforce. The batch job converts the leads to Accounts in Salesforce. Customers visiting their retail stores are also created in Salesforce as Accounts.
The company has noticed a large number of duplicate Accounts in Salesforce. On analysis, it was found that certain customers could interact with its website and also visit the store. The sales associates use Global Search to search for customers in Salesforce before they create the customers.
Which option should a data architect choose to implement to avoid duplicates?
Leveraging duplicate rules in Salesforce to validate duplicates during the account creation process (option A) is the best option to implement to avoid duplicates, as it allows the sales associates to identify and merge duplicate accounts before they are saved. Developing an Apex class that searches for duplicates and removes them nightly (option B) is not a good option, as it may cause data loss or conflicts, and it does not prevent duplicates from being created in the first place. Implementing an MDM solution to validate the customer information before creating Salesforce (option C) is also not a good option, as it may introduce additional complexity and cost, and it does not address the issue of customers interacting with both the website and the store. Building a custom search functionality that allows sales associates to search for customer in real time upon visiting their retail stores (option D) is also not a good option, as it may not be reliable or user-friendly, and it does not leverage the existing Global Search feature.