C_CPI Integration Suite Development Practice Question
You are configuring a Timer sender adapter in SAP Cloud Integration to trigger an integration flow every day at 02:00 AM. The integration flow sends a report to an external system. You notice that the flow sometimes runs twice at the same scheduled time. What is the most likely cause?
⚠ Common exam trap
The trap here is overlooking the clustered nature of the runtime and assuming the Timer adapter inherently runs only once per schedule.
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 integration flow is deployed on multiple runtime nodes without a singleton lock.
In a clustered SAP Cloud Integration environment, Timer-initiated integration flows can execute on multiple runtime nodes if not configured as singleton. This results in duplicate executions at the same scheduled time. Enabling the 'Singleton' option in the Timer adapter ensures that only one node triggers the flow per schedule, preventing duplicates. This is a common configuration oversight when deploying scheduled flows.
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 Timer adapter is configured with a cron expression that includes both a specific time and a wildcard for minutes.
Why it's wrong here
A cron expression with a specific time and a wildcard for minutes would trigger multiple times within that minute, but not necessarily exactly twice at the same time. The issue described is duplicate executions at the same scheduled time, which is more likely due to multiple runtime nodes or overlapping schedules.
- ✓
The integration flow is deployed on multiple runtime nodes without a singleton lock.
Why this is correct
In a clustered environment, if a Timer-initiated integration flow is not configured for singleton execution, each runtime node may trigger the schedule independently, causing duplicate executions. SAP Cloud Integration provides a 'Singleton' option in the Timer adapter to ensure only one node executes the flow per scheduled time. Enabling this prevents duplicate runs.
- ✗
The Timer adapter's time zone is set to UTC, causing it to run at different local times.
Why it's wrong here
Time zone settings affect when the schedule runs relative to local time, but they do not cause duplicate executions at the same time. If the time zone were incorrect, the flow would run at a different hour, not twice at the scheduled hour. Duplicate runs are typically due to multiple runtime nodes.
- ✗
The external system is sending duplicate acknowledgments, causing the flow to retry.
Why it's wrong here
Duplicate acknowledgments from the external system would not cause the Timer adapter to trigger the flow again. The Timer adapter initiates the flow based on schedule, independent of receiver responses. Retries are typically handled by the receiver adapter or error handling, not by the Timer.
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.