Examkin

Question

Difficulty: Very hardDuplicate Management and Matching Rules

CloudKicks uses a Private sharing model for Accounts. An administrator created a custom Matching Rule on Account (matching Account Name and Billing City) and activated a corresponding Duplicate Rule on Account. The Duplicate Rule specifies 'Allow' on Create with both 'Alert' and 'Report' enabled. During testing, sales representatives are still able to create duplicate Account records that match existing accounts in the system without receiving an alert prompt or generating duplicate record sets. The administrator verifies that the Matching Rule and Duplicate Rule are active and that the criteria match the test data. Which configuration adjustment must the administrator make to ensure duplicate accounts owned by other users trigger the alert and report actions?

  1. Modify the Duplicate Rule setting under User Pass-Through from 'Enforce sharing rules' to 'Bypass sharing rules'.Answer
  2. B
    Edit the Matching Rule filter logic to explicitly bypass record ownership access checks.
  3. C
    Change the Duplicate Rule Action on Create setting from 'Allow' to 'Block'.
  4. D
    Re-order the Duplicate Rule execution sequence in Setup to run before Validation Rules.

Answer

Modify the Duplicate Rule setting under User Pass-Through from 'Enforce sharing rules' to 'Bypass sharing rules'.
In Salesforce Duplicate Management, Duplicate Rules can be configured to either 'Enforce sharing rules' or 'Bypass sharing rules'. When set to 'Enforce sharing rules' in an organization with Private OWD, the matching engine only compares records the current user has access to. Changing the rule to 'Bypass sharing rules' enables the system to evaluate all records in the org for duplicates, triggering alerts and logging records to duplicate record sets without revealing confidential fields to unauthorized users.

Step-by-Step Solution

1
Identify the data access constraint affecting duplicate detection.
Since Account Organization-Wide Defaults (OWD) are set to Private, users cannot view Account records owned by other users unless shared.
By default, duplicate rules honor record-level security unless explicitly configured otherwise.
2
Evaluate the duplicate rule security settings.
If a duplicate rule is set to 'Enforce sharing rules', the matching engine only compares the record being created against records visible to the running user.
Hidden duplicate records owned by other users will be ignored during duplicate evaluation.
3
Determine the required administrative setting change.
Changing the duplicate rule configuration to 'Bypass sharing rules' allows the matching engine to search all records across the organization while maintaining existing user UI access boundaries.
This guarantees duplicate detection and reporting across all accounts regardless of owner.

Key Concept

Duplicate Rule Security & Sharing Rule Bypass
Rate this question

Topics

Duplicate Management and Matching Rules

More questions from this topic