C_CPI Integration Suite Development Practice Question
An integration developer needs to persist a message to a data store so that a later integration flow run can check whether the same message was already processed. Which SAP Cloud Integration step should be used to store and retrieve this state across flow executions?
⚠ Common exam trap
Test-takers frequently confuse message-scoped headers and properties with tenant-persistent storage, when only Data Store operations survive beyond a single flow execution.
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
✓
A Write step followed by a Read step in the Data Store operations.
Data Store operations are the tenant-local persistence mechanism for integration flows. Writing the processed message identifier and later reading or selecting it lets a subsequent run detect duplicates or share state across executions. Headers and properties are scoped to a single exchange, and no Persist step exists, so the Data Store approach is the correct fit.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A Persist step configured with the message payload.
Why it's wrong here
There is no step named Persist in SAP Cloud Integration. Persistence across runs is achieved through Data Store operations, which offer Write, Read, Select, and Delete actions. Referencing a nonexistent step indicates a misunderstanding of the available palette and would not fulfill the requirement.
- ✓
A Write step followed by a Read step in the Data Store operations.
Why this is correct
Data Store operations provide persistent storage within the tenant, with Write to store an entry and Read or Select to retrieve it in a later run. Using Write to persist the processed message and Read or Select to check for its existence in a subsequent execution supports exactly the cross-run state requirement described.
- ✗
A JMS queue sender adapter configured with a durable subscription.
Why it's wrong here
JMS queues provide asynchronous messaging and can retain messages, but they are designed for decoupling producers and consumers rather than for storing a lookup record that a later flow queries by key. Using a queue for idempotency checks adds unnecessary complexity compared with the dedicated Data Store operations.
- ✗
A Content Modifier that sets a property with the message identifier.
Why it's wrong here
A Content Modifier stores values only within the current message exchange as headers or properties. When the flow execution ends, those values are discarded, so a later flow run cannot see them. This makes it unsuitable for checking whether a message was processed in a previous, separate execution.
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.