C_ARSUM Ariba Supplier Management Practice Question
Exhibit
{
"rule": "Duplicate_Prevention",
"match_fields": ["Tax_ID", "DUNS_Number"],
"action": "Block",
"notify": "Procurement_Admin"
}Refer to the exhibit. What happens when a user attempts to add a new supplier with the same Tax ID as an existing supplier?
⚠ Common exam trap
Candidates often assume the system will allow the duplicate and flag it later, rather than recognizing that the 'Block' configuration provides immediate, real-time protection against data fragmentation.
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
✓
The entry is blocked and the administrator is notified.
The 'Block' action prevents the creation of a duplicate record, protecting the integrity of the master data. The system simultaneously notifies the 'Procurement_Admin', allowing them to investigate why a duplicate was attempted. This is a critical governance mechanism; it prevents fragmented supplier records that could lead to disjointed reporting, incorrect tax filings, and the inability to gain a holistic view of the spend and risk exposure associated with the vendor entity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The record is merged automatically with the existing supplier.
Why it's wrong here
Automatic merging is risky and discouraged, as it can lead to unintentional overwriting of data or incorrect mapping. The system blocks the entry to force an manual, informed review by an administrator who can properly determine if the new entry represents a new site or is truly a duplicate that should be rejected.
- ✓
The entry is blocked and the administrator is notified.
Why this is correct
The 'Block' action stops the creation of the duplicate, and the 'notify' field ensures that the procurement team is alerted. This allows the administrator to take control, verify the information, and ensure that the database remains clean and free of redundant vendor entities that would otherwise complicate downstream financial processes.
- ✗
The user is allowed to proceed but with a warning flag.
Why it's wrong here
The policy action is 'Block', not 'Warn'. Warning flags are often ignored by users, which would allow the duplicate record to be created, leading to data quality issues. A strict block is necessary to maintain the integrity of the supplier database and prevent the accumulation of duplicate records that degrade data consistency.
- ✗
The duplicate is sent to the supplier to confirm their identity.
Why it's wrong here
The policy is designed for internal governance and does not involve the supplier in the validation phase. Automatically emailing the supplier would disclose internal system logic and potentially cause confusion. The responsibility for ensuring database uniqueness rests entirely with the procurement organization, handled through internal administrative review, not external communication.
About these practice questions
This C_ARSUM question is part of Courseiva's 250-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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 SAP exam blueprint
This C_ARSUM practice question is part of Courseiva's free SAP 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 C_ARSUM exam.