C_CPI Integration Suite Development Practice Question
An integration developer must ensure that an integration flow processing bank transfer messages is idempotent. The same transfer notification can be delivered more than once by the sender, and duplicate processing would cause a double payment. The developer needs the tenant to detect and discard duplicates automatically. Which configuration should be used?
⚠ Common exam trap
A common mix-up: candidates confuse transport-level exactly-once messaging with payload-level idempotency, when only the Idempotent Process Call option deduplicates distinct repeated notifications.
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
✓
Enable the 'Idempotent Process Call' option on the sender adapter and specify the message ID element for duplicate detection.
The Idempotent Process Call option on a sender adapter provides built-in duplicate detection by hashing a designated message ID and rejecting repeats during the retention window. Pointing it at the transfer notification's unique identifier makes the tenant discard duplicates before business logic executes, which is the reliable way to prevent a double payment.
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 Groovy script that queries the Data Store for the transfer ID and throws an exception when a match is found.
Why it's wrong here
A custom Groovy script querying a Data Store can detect duplicates, but it relies on developer-written logic and error handling rather than a built-in mechanism. It also adds latency and maintenance burden, and an unhandled exception would end the flow with a failure instead of cleanly discarding the duplicate notification.
- ✗
Configure the JMS sender adapter to use a message retention policy and enable exactly-once delivery on the queue.
Why it's wrong here
JMS exactly-once semantics protect against duplicate consumption of a single queued message by the messaging layer. They do not deduplicate repeated notifications that arrive as distinct messages from the sender, so two separately produced transfer notifications would both be consumed and processed, risking a double payment.
- ✗
Enable the 'Idempotent Process Call' option on the Process Direct adapter and set a retention period.
Why it's wrong here
The Process Direct adapter connects flow steps inside the same tenant and does not expose a persisted idempotency store. Its options govern local invocation behavior, not duplicate detection across separate inbound messages, so a repeated transfer notification would still be processed again and could trigger a second payment.
- ✓
Enable the 'Idempotent Process Call' option on the sender adapter and specify the message ID element for duplicate detection.
Why this is correct
The Idempotent Process Call option on a sender adapter stores a hash of the configured message ID and discards messages whose hash was already seen within the retention window. Pointing it at the transfer notification's unique ID lets the tenant detect and drop duplicates automatically before the flow logic runs.
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.