C_CPI Integration Suite Development Practice Question
An integration developer is troubleshooting an integration flow whose SFTP sender adapter intermittently processes the same file twice. The partner writes files with a temporary extension and renames them once fully uploaded. Which adapter setting should be reviewed first to prevent duplicate processing?
⚠ Common exam trap
The trap here is focusing on polling frequency or filename filters, when duplicate consumption is actually controlled by what the adapter does with a file after it has been successfully read.
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
✓
The Post-Processing setting that marks consumed files, such as moving or deleting them after successful processing
Duplicate reads occur because the adapter has no memory of previously consumed files unless post-processing changes their state. Configuring a post-processing action such as Move, Delete, or Archive after successful processing removes or relocates the file so subsequent polls cannot match it again. Poll interval, filename patterns, and reconnect settings all affect detection or connectivity, not consumption tracking, so they cannot resolve the duplication.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The Post-Processing setting that marks consumed files, such as moving or deleting them after successful processing
Why this is correct
Post-processing actions such as Move, Delete, or archiving change the file's state or location after a successful read, so the same physical file no longer matches on the next poll. This is the standard mechanism for exactly-once-style consumption with the SFTP sender adapter and directly prevents the reported duplicate processing.
- ✗
The Poll Interval configured on the SFTP sender channel
Why it's wrong here
The Poll Interval only controls how frequently the adapter checks the directory for new files. Shortening or lengthening it changes detection latency but does not by itself guarantee that an already-consumed file is excluded from a later poll, so it does not address the root cause of duplicate processing.
- ✗
The file name pattern restriction, for example limiting reads to files ending in .done
Why it's wrong here
A filename pattern narrows which files the adapter considers, which is useful for ignoring temporary files, but it does not track what has already been processed. Once the file is renamed to its final name, the pattern still matches it on every poll, so duplicates remain possible unless consumption tracking is configured.
- ✗
The Maximum Reconnect Attempts and Retry Interval values on the SFTP channel
Why it's wrong here
Reconnect and retry settings govern how the adapter recovers from network or authentication failures when opening the SFTP session. They influence resilience of the connection, not whether a file that was already read successfully is read again, so tuning them will not stop the duplication observed in this flow.
Visual reference
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.