Question

Difficulty: MediumDuplicate Management and Matching Rules

A Salesforce administrator at Meridian Global Consulting is tasked with setting up duplicate detection for custom Lead records. What is the correct sequence of administrative steps required to build, configure, and activate this duplicate management process?

  1. 1Create a custom Matching Rule specifying the exact and fuzzy field comparison criteria.
  2. 2Activate the custom Matching Rule.
  3. 3Create a new Duplicate Rule for the object and select the activated Matching Rule.
  4. 4Configure the enforcement actions (such as Alert, Report, or Block) for record creation and edits.
  5. 5Activate the Duplicate Rule.

Answer

The correct administrative sequence is: 1) Create a custom Matching Rule specifying comparison criteria, 2) Activate the custom Matching Rule, 3) Create a new Duplicate Rule and select the activated Matching Rule, 4) Configure the enforcement actions (Alert, Report, or Block), and 5) Activate the Duplicate Rule.
The correct order requires creating the matching rule criteria first, activating that matching rule so it becomes available, referencing it within a new duplicate rule, specifying the operational actions (Block/Allow/Report), and finally activating the duplicate rule to enforce the setup.

Step-by-Step Solution

1
Create the custom Matching Rule.
Establishes the specific algorithm and field-level criteria used to compare records.
Matching logic must exist before a duplicate rule can evaluate incoming record data.
2
Activate the Matching Rule.
Makes the matching rule active and selectable within the setup framework.
Salesforce duplicate rules cannot reference or process inactive matching rules.
3
Create the Duplicate Rule and associate the active Matching Rule.
Binds the matching logic to the target object and record operation triggers.
Duplicate rules define the execution context and scope for matching criteria.
4
Set the operational actions (Block or Allow with Alert/Report).
Defines user experience and data governance behavior when duplicates are flagged.
Enforcement settings determine whether record saving is stopped or merely logged.
5
Activate the Duplicate Rule.
Enforces duplicate detection in real time for end users.
Duplicate rules remain ineffective until explicitly activated.

Key Concept

Duplicate management setup requires creating and activating matching logic first, followed by building the duplicate rule, setting its execution actions, and activating the duplicate rule.
Rate this question