C_ARSUM Ariba Supplier Management Practice Question
Exhibit
{
"policy_id": "SUPP_001",
"block_registration": true,
"bypass_for_internal": false,
"min_risk_score": 75
}Refer to the exhibit. A company implements this JSON policy in their SAP Ariba Supplier Risk environment. What is the immediate effect when a supplier registration is initiated for a vendor with a risk score of 80?
⚠ Common exam trap
Exam takers often misread JSON threshold conditions, failing to notice whether a score exceeding the defined limit triggers a block or a warning.
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 registration is automatically blocked.
The exhibit displays a risk policy that blocks registrations when the vendor's risk score exceeds 75. Since the supplier has a score of 80, the system triggers the 'block_registration' boolean. This prevents the onboarding process from proceeding, protecting the company from engaging with high-risk entities. Understanding these JSON-based policy configurations is critical for administrators managing automated risk mitigation strategies within the SAP Ariba Supplier Lifecycle and Risk suite.
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 registration proceeds normally.
Why it's wrong here
The policy explicitly sets 'block_registration' to true for scores above 75. Because 80 exceeds this threshold, the system enforces the block. Therefore, the registration process will not proceed as expected, and the supplier will be effectively blocked from moving forward in the current onboarding workflow.
- ✓
The registration is automatically blocked.
Why this is correct
The JSON policy defines a minimum risk score threshold of 75. Any supplier with a score of 80 meets the criteria for the block. Consequently, the 'block_registration' setting is activated, which immediately stops the registration process, ensuring that the company maintains its internal risk management protocols for high-risk vendors.
- ✗
The registration requires manual approval.
Why it's wrong here
The policy configuration provided does not define an 'approval' workflow or a 'manual_review' flag. It specifies a hard block on the registration. The system logic dictates that once the blocking condition is satisfied, the process terminates rather than escalating to a human user for further intervention or approval.
- ✗
The policy is ignored due to internal bypass.
Why it's wrong here
The 'bypass_for_internal' flag is explicitly set to false in the JSON configuration. This confirms that there is no mechanism to bypass the risk block for internal users. The rule is strictly enforced regardless of the origin of the request or the internal user's specific role permissions.
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.