Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Data Architect Topic 2 Question 19 Discussion

Actual exam question for Salesforce's Data Architect exam
Question #: 19
Topic #: 2
[All Data Architect Questions]

Universal Containers (UC) is facing data quality issues where Sales Reps are creating duplicate customer accounts, contacts, and leads. UC wants to fix this issue immediately by prompting users about a record that possibly exists in Salesforce. UC wants a report regarding duplicate records. What would be the recommended approach to help UC start immediately?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Casandra
1 months ago
Triggers? Matching criteria? Nah, I'm going with Option B. Keeping it simple and using the standard features is the way to go. Less code, more productivity!
upvoted 0 times
...
Keena
1 months ago
Option A looks good, but triggers can be tricky to maintain. I'd rather let Salesforce handle the duplicate detection for me.
upvoted 0 times
...
Lea
1 months ago
Haha, Option D with a custom matching criteria? That's like trying to reinvent the wheel. Why not use the tools Salesforce provides?
upvoted 0 times
Alishia
13 days ago
A) Create an after insert and update trigger on the account, contact and lead, and send an error if a duplicate is found using a custom matching criteria.
upvoted 0 times
...
...
Queen
1 months ago
I'd go with C. Blocking the user from creating duplicates is the best way to ensure data quality, even if it's a bit more restrictive.
upvoted 0 times
Aracelis
18 days ago
That sounds like a good idea. Preventing duplicates from being created in the first place is key.
upvoted 0 times
...
Chau
19 days ago
C) Create a duplicate rule for account, lead, and contact, use standard matching rules for these objects, and set the action to block for both creates and edits.
upvoted 0 times
...
...
Buck
2 months ago
Option B seems like the way to go. Duplicate rules are a built-in feature, and using standard matching with report and alert is a good starting point.
upvoted 0 times
Martina
8 days ago
User 1: I think option B is the best choice.
upvoted 0 times
...
Phuong
14 days ago
User 4: Let's implement it quickly to improve our data quality.
upvoted 0 times
...
Giovanna
1 months ago
User 3: That way we can catch duplicates right away and take action.
upvoted 0 times
...
Cortney
1 months ago
User 2: Agreed, duplicate rules with standard matching and alerts sound like a good plan.
upvoted 0 times
...
Mabel
1 months ago
User 1: I think we should go with option B.
upvoted 0 times
...
...
Justine
2 months ago
That's a good point, Melissa. Triggers can definitely help in real-time prevention of duplicate records. UC should consider that as well.
upvoted 0 times
...
Melissa
2 months ago
I disagree, I believe option A is more effective. By using triggers, UC can prevent duplicates from being created in the first place.
upvoted 0 times
...
Justine
2 months ago
I think option B is the best approach. It will help UC identify duplicates and take action immediately.
upvoted 0 times
...
Candra
2 months ago
That's a good point, Aron. Option A does provide real-time prevention of duplicates. It's a tough choice between the two options.
upvoted 0 times
...
Aron
2 months ago
I disagree, I believe option A is more effective. By creating triggers with custom matching criteria, UC can prevent duplicates right at the point of creation or update.
upvoted 0 times
...
Candra
2 months ago
I think option B is the best approach. It will help UC identify and report duplicate records using standard matching rules.
upvoted 0 times
...

Save Cancel