C_CPI Integration Suite Development Practice Question
An integration developer is building an integration flow in SAP Cloud Integration that must process very large XML payloads. The flow splits the message using an Iterating Splitter, but the developer notices that the entire message is being loaded into memory before splitting, causing OutOfMemory errors. Which splitter type should be used to process the message in a streaming fashion?
⚠ Common exam trap
The trap here is assuming that any splitter type will automatically stream the payload, when in fact only the Streaming Splitter uses a streaming parser to avoid loading the entire message into memory.
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
✓
Streaming Splitter
The Streaming Splitter is designed to handle large messages by parsing the input as a stream rather than building a complete DOM in memory. This prevents the OutOfMemory errors caused by the Iterating Splitter, which loads the entire message. For very large XML payloads, the streaming approach is the appropriate solution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Iterating Splitter
Why it's wrong here
The Iterating Splitter is the one already in use and is the cause of the memory issue because it reads the whole payload into memory. It iterates over the split elements but does not stream. Choosing it again would not change the behavior and the OutOfMemory errors would persist. It is not the streaming alternative.
- ✗
General Splitter
Why it's wrong here
The General Splitter splits a message based on an XPath expression but still loads the entire message into memory before performing the split. It does not stream the payload, so for very large XML messages it would not resolve the OutOfMemory condition. It is suitable for moderate-sized messages where the full DOM can be held in memory.
- ✗
PKCS7/CMS Splitter
Why it's wrong here
The PKCS7/CMS Splitter is designed to extract the signed content from a PKCS#7 or CMS structure, not to split arbitrary XML payloads. It is unrelated to the scenario of splitting large XML messages and would not help with memory consumption. Using it here would fail because the input is not a PKCS7/CMS message.
- ✓
Streaming Splitter
Why this is correct
The Streaming Splitter processes the incoming message as a stream, reading and splitting it incrementally without loading the entire payload into memory. This is exactly what is needed for very large XML messages to avoid OutOfMemory errors. It uses a StAX parser to emit split messages as they are read, making it the correct choice for high-volume, memory-constrained scenarios.
About these practice questions
Courseiva writes every C_CPI question from scratch — 218 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_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.