C_CPI Integration Suite Development Practice Question
An integration developer is troubleshooting an integration flow that intermittently fails when writing to an SAP S/4HANA system with the OData V2 receiver adapter. Monitoring shows the payload is valid and credentials are correct, but some messages fail with a timeout under peak load. Which TWO configuration changes should the developer apply to improve resilience? (Choose two.)
⚠ Common exam trap
The trap here is treating a protocol or structural change as a resilience fix, when the actual levers are timeout values and retry behavior scoped to safe operations.
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
✓
Increase the connection and response timeout values in the OData receiver adapter
Intermittent timeouts under peak load point to the adapter giving up before a busy backend responds, and to transient network or backend hiccups. Raising the connection and response timeouts lets slow-but-successful calls complete, while retrying idempotent reads on transient errors absorbs momentary failures without risking duplicate writes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Switch the receiver adapter to the SOAP protocol to reduce overhead
Why it's wrong here
Changing the protocol does not address backend processing time and would require rebuilding the request and response handling for a different interface contract. The S/4HANA service being called is exposed as OData, so a SOAP call would not map to the same endpoint and would likely fail outright.
- ✓
Increase the connection and response timeout values in the OData receiver adapter
Why this is correct
Timeouts under peak load typically mean the backend takes longer to respond than the adapter is willing to wait. Raising the connection and response timeout values gives the S/4HANA system more time to complete slow requests, directly reducing the intermittent timeout failures without changing the payload or credentials.
- ✗
Move the OData call into a Local Integration Process to isolate it
Why it's wrong here
A Local Integration Process is a structural construct for reusing or organizing flow logic, not a resilience mechanism. It does not alter timeout behavior, retry behavior, or backend load, so moving the call there leaves the intermittent timeout condition unchanged.
- ✓
Configure the adapter's retry settings to retry idempotent read operations on transient errors
Why this is correct
Retrying transient failures is a standard resilience pattern, and limiting retries to idempotent operations such as reads avoids duplicate side effects. This smooths over peak-load hiccups while keeping writes safe, so intermittent timeouts on read calls no longer surface as message failures.
- ✗
Disable the CSRF token handling in the adapter to save a round trip
Why it's wrong here
CSRF token handling is required for write operations against S/4HANA OData services. Disabling it would cause the backend to reject the modifying requests with a security error, replacing intermittent timeouts with consistent authorization failures, so it worsens rather than improves resilience.
About these practice questions
One of 218 original C_CPI 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 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.