C_CPI Integration Suite Development Practice Question
An integration developer is configuring an integration flow that receives messages from an HTTPS sender adapter. The flow must ensure that messages are processed exactly once, even if the sender retries due to a timeout. Which feature should be configured to achieve this?
⚠ Common exam trap
The trap here is assuming that retry settings or duplicate detection options on the sender adapter provide exactly-once processing, when idempotency must be explicitly implemented.
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 the Idempotent Process Call step with a message ID derived from the incoming request
Exactly-once processing in SAP Cloud Integration is achieved through idempotency. The Idempotent Process Call step uses a unique message ID to detect and skip duplicates. By deriving this ID from the incoming HTTPS request, the flow ensures that retries do not result in duplicate processing. Other options either do not apply to the HTTPS sender or do not provide idempotency, so they fail to meet the requirement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable the 'Duplicate Message Detection' option in the HTTPS sender adapter
Why it's wrong here
Duplicate Message Detection is not a standard option in the HTTPS sender adapter. While some adapters support idempotent processing, the HTTPS sender adapter does not provide a direct duplicate detection setting. The developer must use a different mechanism, such as the Idempotent Process Call or a JMS queue with message ID deduplication, to ensure exactly-once processing.
- ✗
Set the 'Retry' option to zero on the HTTPS sender adapter
Why it's wrong here
Setting retry to zero on the sender adapter does not prevent duplicate processing; it only affects the adapter's behavior on errors. The sender may still retry externally, leading to duplicate messages. The requirement is to ensure exactly-once processing despite retries, which requires idempotency, not retry configuration. Therefore, this option does not achieve the goal.
- ✓
Use the Idempotent Process Call step with a message ID derived from the incoming request
Why this is correct
The Idempotent Process Call step in SAP Cloud Integration ensures that a message is processed only once based on a unique message ID. By deriving the ID from the incoming request, such as a business key or a header, the step can detect and discard duplicate messages. This provides exactly-once processing semantics even if the sender retries, making it the correct solution for this scenario.
- ✗
Configure the JMS sender adapter with exactly-once quality of service
Why it's wrong here
The JMS adapter supports quality of service levels, but the scenario specifies an HTTPS sender adapter. JMS cannot be applied to an HTTPS sender. While JMS can provide exactly-once delivery in some configurations, it is not the right tool when the sender is HTTPS. The developer must use a mechanism compatible with the HTTPS adapter, such as Idempotent Process Call.
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.