An administrator at CloudScale Systems creates and activates a custom Matching Rule on the Account object using exact match logic on Account Name and Billing City. However, sales representatives are still able to create duplicate accounts without seeing any warning prompts or blocked attempts, and no duplicates appear in duplicate record reports. What step did the administrator forget to perform to enforce duplicate handling?
- The administrator must create and activate a Duplicate Rule that references the custom Matching Rule to define enforcement actions like alert, block, or report.Answer
- BThe administrator must assign the active Matching Rule directly to user profiles under Object Manager field permissions.
- CThe administrator must deploy Apex trigger logic to invoke matching rules, as matching rules only execute automated batch jobs by default.
- DThe administrator must replace the custom Matching Rule with a standard Account Matching Rule, as custom matching rules only operate on custom objects.
Answer
The administrator must create and activate a Duplicate Rule that references the custom Matching Rule to define enforcement actions like alert, block, or report.
Matching rules only specify the comparison criteria used to identify duplicate records (e.g., exact match on Account Name and Billing City). To actually prevent duplicates or alert users, an administrator must configure and activate a Duplicate Rule that references that Matching Rule and specifies the desired action, such as alerting the user, blocking the save operation, or generating duplicate record reports.
Step-by-Step Solution
Key Concept
Matching rules define how duplicate records are identified, whereas duplicate rules define what happens when duplicates are detected.