SF-Data-Arch Salesforce Data Management Practice Question
Universal Containers wants to ensure data quality by preventing the creation of duplicate Leads from various sources. The architect recommends matching rules and duplicate rules. Which action should the architect take to ensure that users are alerted to potential duplicates during manual entry while blocking automated integrations?
⚠ Common exam trap
Candidates often think duplicate rules apply globally, failing to recognize that they can configure different actions for manual UI entry versus automated API integrations within the same rule.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set 'Report' for record creation and 'Block' for API insertion.
To achieve this, the architect must configure duplicate rules with distinct settings for user-based versus integration-based scenarios. By setting the 'Report' action for user-facing rules, the UI displays an alert, while selecting 'Block' for API-based rules prevents duplicates from being inserted via integration tools. This tiered approach maintains data integrity across different entry points without hindering necessary manual workflows during prospect record creation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable 'Block' for both user-facing and integration-based duplicate rules.
Why it's wrong here
Blocking both channels prevents users from manually entering valid but potentially matching leads, which negatively impacts productivity and prevents legitimate data entry. The business requirement explicitly asks for alerts in the UI, which this configuration would fail to provide by forcing a hard block on every creation attempt.
- ✗
Apply 'Report' to the record creation rule and ignore the API settings.
Why it's wrong here
The 'Report' setting only generates a duplicate record event for tracking; it does not block the creation of duplicates from integrations. Simply ignoring API settings leaves the system vulnerable to junk data, failing the specific requirement to prevent duplicates from automated sources through a hard block mechanism.
- ✓
Set 'Report' for record creation and 'Block' for API insertion.
Why this is correct
This configuration directly maps to the requirements. The 'Report' action allows users to proceed after an alert, facilitating manual data entry, while the 'Block' action on the API ensures that automated integration processes cannot bypass duplicate prevention, effectively maintaining high data quality across all system interaction types.
- ✗
Use a third-party AppExchange solution exclusively for integration rules.
Why it's wrong here
While third-party solutions provide advanced matching logic, native Salesforce duplicate rules are capable of handling these requirements natively without additional costs or dependencies. Relying on an external tool for standard duplicate management increases architectural complexity and maintenance overhead without providing a tangible benefit for these specific business needs.
About these practice questions
One of 222 original SF-Data-Arch practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Data-Arch practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Data-Arch exam.