C_CPI Integration Suite Development Practice Question
An integration developer is configuring a Request Reply step in an integration flow that calls an external REST API. The API returns a JSON response that must be merged with the original request payload before being sent to the receiver. Which pattern should the developer use?
⚠ Common exam trap
The trap here is assuming Request Reply automatically retains the original payload or that Multicast merges branch outputs, when in fact the body is replaced and merging must be designed explicitly.
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
✓
Use a Request Reply step, then a Message Mapping or Groovy Script step to combine the response with the saved original payload.
A Request Reply step replaces the message body with the API response, so the original request payload must be preserved separately and then merged with the response using a mapping or script. This is the standard enrichment pattern in SAP Cloud Integration.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a Splitter step to separate the request and response, then a Gather step to merge them.
Why it's wrong here
Splitter and Gather are designed for splitting a single message into multiple messages and recombining them, not for merging a request with its response from a remote call. Applying them here would not preserve the original request payload alongside the API response. This pattern is unrelated to the enrichment requirement.
- ✗
Use a Multicast step with two branches, one calling the API and one retaining the original, then rely on the multicast to merge the outputs.
Why it's wrong here
Multicast creates parallel branches that each receive a copy of the message, but it does not automatically merge the outputs into one message. The branches execute independently, and there is no built-in join that combines the API response with the original payload. The developer would still need an explicit merge step.
- ✗
Use a Content Enricher step to merge the API response into the original message.
Why it's wrong here
Content Enricher is used to enrich a message with data from another source, but in SAP Cloud Integration it is typically implemented with a Request Reply and a mapping step. It is not a standalone step that automatically merges a Request Reply response with the original payload. The developer still needs to design the merge logic explicitly, so naming the pattern alone does not solve the configuration.
- ✓
Use a Request Reply step, then a Message Mapping or Groovy Script step to combine the response with the saved original payload.
Why this is correct
The Request Reply step sends the request and receives the response, but it replaces the message body by default. To merge, the developer must preserve the original payload, for example in a property or by using a multicast before the call, and then combine it with the response using a mapping or script. This is the correct pattern for response merging.
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.