C_CPI Integration Suite Development Practice Question
An integration developer needs the integration flow to continue processing when a receiver returns an HTTP 404, because a missing resource is a valid business outcome. The developer wants the flow to inspect the status code and route the message accordingly instead of failing. Which exception handling configuration should the developer apply to the receiver call?
⚠ Common exam trap
The trap here is assuming any non-2xx response always aborts the flow, when the adapter's throw-on-failure setting controls whether the status is surfaced as data.
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
✓
Disable the 'Throw exception on failure' option so the status code is written to the message and can be evaluated by a Router
To treat an HTTP error status as data rather than a fault, the receiver call must be configured not to raise an exception on failure. The status code then becomes available on the message, and a Router can branch on it, letting the missing-resource case follow the business-valid path while other errors are handled separately.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set the receiver adapter's Retry configuration to retry on all HTTP error codes
Why it's wrong here
Retry is designed for transient failures such as timeouts or 5xx responses. Retrying a 404 simply repeats a request that will never succeed, and after the retries are exhausted the flow still fails. It does not make the 404 available for inspection or routing, so it does not meet the requirement.
- ✗
Set the Exchange Property to store the response and enable the 'Throw exception on failure' option
Why it's wrong here
Enabling the option to throw an exception on failure does the opposite of the requirement: it forces the receiver call to raise an error for the 404 and stop normal processing. Storing the response in an exchange property is useful for inspection, but combined with throwing, the main flow no longer continues normally.
- ✗
Configure the receiver call as an Exception Subprocess with a condition on the error code
Why it's wrong here
An Exception Subprocess handles errors that have already been raised and terminated the main flow. While it can inspect error details, it runs on a separate error path and cannot resume the main flow's normal routing after the 404, so the desired inline routing based on the status code is not achieved.
- ✓
Disable the 'Throw exception on failure' option so the status code is written to the message and can be evaluated by a Router
Why this is correct
With the throw-on-failure option disabled, the adapter does not raise an exception for HTTP error codes. The response, including the status code, is placed on the message, allowing a subsequent Router or condition to evaluate CamelHttpResponseCode and route the missing-resource case along the intended business path.
About these practice questions
This C_CPI question is part of Courseiva's 218-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_CPI 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_CPI exam.