Universal Containers has a Sales Cloud implementation for a sales team and an enterprise resource planning (ERP) as a customer master. Sales teams are complaining about duplicate account records and data quality issues with account data.
Which two solutions should a data architect recommend to resolve the complaints? (Choose two.)
To resolve the complaints about duplicate account records and data quality issues, integrating Salesforce with the ERP and making the ERP the system of truth ensures that the data in Salesforce remains consistent and up-to-date. Additionally, implementing a de-dupe solution within Salesforce addresses the issue of existing duplicate records by merging them and establishes clear account ownership rules to prevent future duplicates. These combined actions ensure both immediate resolution of the duplicate issue and maintain data quality over time.
B. Integrate Salesforce with ERP, and make ERP as system of truth. This would ensure that the data in Salesforce is always up-to-date and consistent with the data in the ERP system, which is the customer master. D. Implement a de-dupe solution and establish account ownership in Salesforce. This would help to prevent the creation of duplicate account records in Salesforce and improve data quality. Establishing account ownership would also help to manage the account data more effectively. These solutions would address both the issue of duplicate records and the data quality issues that the sales teams are experiencing
I would say B and C make sense together. ERP should stay the system of truth (system of record) (D). And if ERP is the system of truth we should not make deduplication in a slave system (this time Salesforce. (A)
Option C, “Build a nightly sync job from ERP to Salesforce,” could indeed be a part of the solution. However, it doesn’t address the issue of duplicate records already existing in the system. On the other hand, option D, “Implement a de-dupe solution and establish account ownership in Salesforce,” directly addresses the problem of duplicate records. It suggests implementing a solution to identify and merge duplicates, and establishing clear ownership rules for accounts to prevent future duplicates. Therefore, while both options could be part of a comprehensive solution, option D is more directly aligned with resolving the complaints of the sales team. It’s also important to note that a sync job (option C) would ideally be part of an overall integration strategy with the ERP system (option B), rather than a standalone solution.
Data Quality issues are solved using ERP as system of truth (B). Duplicate issues would be solved with a de-dupe solution (D). B and C together would not solve dupe issues
B is right because we're told that the master is in ERP, so we want ERP as truth. However, the second part needs to consider how we de-dupe. That leaves A,C,or D. C doesn't make sense because it doesn't consider de-duping. While A could apply, it doesn't make sense, as thneeb points out, we wouldn't make dedupe in the child system if ERP is the parent, so the better answer is D. Also as tobicky points out, it's easier to maintain the account going forward if ownership is established.