C_ARSUM Ariba Supplier Management Practice Question
Exhibit
{ "policy": "Supplier_Registration_Approval", "version": "2.1", "rules": { "auto_approve": "false", "require_manager_signoff": "true", "enable_fallback": "true" } }Refer to the exhibit. Given the provided JSON policy, what will happen if the manager is absent when a supplier registration is submitted?
⚠ Common exam trap
Candidates often assume the process will simply fail or error out if a manager is absent, overlooking the system's built-in fallback and escalation logic defined in the policy.
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 system will escalate to the manager's supervisor or default approver.
The 'enable_fallback' rule set to 'true' in the policy ensures that the system does not hang indefinitely when a primary approver is unavailable. In SAP Ariba, this triggers the workflow escalation or default routing mechanism. This functionality is critical for keeping procurement processes moving without manual intervention for every absence, ensuring that supplier registration bottlenecks do not delay the onboarding cycle for business-critical vendors.
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 will be automatically approved by the system.
Why it's wrong here
The auto_approve rule is explicitly set to 'false'. Therefore, the system will not perform an automatic approval regardless of the manager's status. The policy requires a formal sign-off, meaning system-level approval is strictly prohibited for registration requests to maintain internal control and auditability of the vendor.
- ✓
The system will escalate to the manager's supervisor or default approver.
Why this is correct
With enable_fallback set to true, the workflow engine automatically reroutes the approval task to the defined fallback approver or supervisor. This ensures that the registration process continues, preventing operational stalls that occur when primary stakeholders are unavailable, thus maintaining the efficiency of the overall supplier registration lifecycle.
- ✗
The registration will be rejected due to a lack of sign-off.
Why it's wrong here
Rejection would be an inefficient outcome for a registration workflow. The policy defines a fallback mechanism, which is intended to facilitate completion, not termination. The process is designed to find an alternative approval path rather than failing the request, which would require the supplier to resubmit their application.
- ✗
The system will throw an error and log a critical failure.
Why it's wrong here
The policy includes an enabled fallback rule, which is specifically designed to prevent system errors. A failure log would imply a configuration gap, whereas the system is behaving as expected by utilizing the fallback path to manage the missing approval, thereby ensuring consistent process execution and system stability.
About these practice questions
Courseiva writes every C_ARSUM question from scratch — 250 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.