C_CPI Integration Suite Development Practice Question
You are configuring a JMS receiver adapter in SAP Cloud Integration to send messages to a queue. The queue is configured with a maximum message size of 10 MB. During testing, you notice that messages larger than 10 MB are being rejected and the integration flow fails. Which action should you take to handle this situation gracefully?
⚠ Common exam trap
The trap here is thinking that the JMS adapter can automatically split messages or that retrying will solve a size limit issue, when in fact the split must be done explicitly in the flow.
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
✓
Add a Splitter step before the JMS receiver adapter to divide the large message into smaller messages that are within the size limit.
When a JMS queue enforces a maximum message size, the integration flow must ensure that messages sent do not exceed that limit. Splitting the large message into smaller parts using a Splitter step allows each part to be sent separately and successfully. This is a standard pattern for handling large payloads with size-constrained receivers.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Add a Splitter step before the JMS receiver adapter to divide the large message into smaller messages that are within the size limit.
Why this is correct
The Splitter step can break a large payload into multiple smaller messages based on an XPath expression or other criteria. Each resulting message will be smaller and can be sent individually to the JMS queue, respecting the 10 MB limit. This is the correct approach to handle large messages when the queue has a size restriction, ensuring all data is processed without rejection.
- ✗
Enable the 'Split Message' option in the JMS receiver adapter to break large messages into smaller chunks.
Why it's wrong here
The JMS receiver adapter does not have a 'Split Message' option. Splitting must be done in the integration flow using a Splitter step before the JMS adapter. Enabling such an option is not possible, and even if it were, splitting a single logical message might not be appropriate for the business process. The adapter itself does not provide this functionality.
- ✗
Configure a retry mechanism with a backoff policy in the JMS receiver adapter to resend the message until it fits.
Why it's wrong here
Retrying will not reduce the message size; the message will still exceed the queue's maximum size and continue to be rejected. A backoff policy only helps with transient errors like network issues, not with permanent size constraints. The message would never succeed, leading to endless retries and potential resource exhaustion.
- ✗
Use a Content Modifier to set the JMS message size property to a larger value before the JMS receiver adapter.
Why it's wrong here
The maximum message size is enforced by the JMS broker, not by a property that can be overridden in the message. Setting a property would not change the broker's configuration or the actual payload size. The broker will still reject the message based on its own limits, so this approach is ineffective.
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.