C_CPI Integration Suite Development Practice Question
An integration flow uses a multicast step with two branches. The first branch writes to an SFTP server and the second branch sends an alert email. The developer observes that when the SFTP write fails, the email is never sent. Which multicast configuration change ensures the email branch still executes when the SFTP branch fails?
⚠ Common exam trap
The trap here is assuming branch execution order or exception subprocesses control sibling behavior, when the multicast's 'Stop on Exception' flag is the actual switch.
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
✓
Disable 'Stop on Exception' on the multicast so remaining branches continue after a branch fails.
The multicast step's 'Stop on Exception' option controls whether a failing branch aborts the remaining branches. Disabling it makes the runtime process each branch independently, logging the failure of the SFTP branch while still executing the email branch. This isolation is what guarantees the alert is sent despite the SFTP error.
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 'Stop on Exception' on the multicast and add an Exception Subprocess to the flow.
Why it's wrong here
Enabling 'Stop on Exception' explicitly halts remaining branches when one branch throws an error, which is the opposite of what is needed. Adding an Exception Subprocess at flow level handles the error after the multicast aborts, but the email branch would already have been skipped. This combination worsens the problem rather than solving it.
- ✓
Disable 'Stop on Exception' on the multicast so remaining branches continue after a branch fails.
Why this is correct
When 'Stop on Exception' is disabled, the multicast step treats each branch independently: if one branch raises an exception, the runtime logs it but continues executing the remaining branches. Disabling this option therefore allows the email branch to run even when the SFTP write fails, which is exactly the required behavior.
- ✗
Wrap the SFTP branch in a Local Integration Process and set its quality of service to Exactly Once.
Why it's wrong here
Moving the SFTP logic into a Local Integration Process changes the flow's structure but not the multicast's error-handling semantics. The quality of service setting controls message delivery guarantees, not whether sibling branches continue after a failure. Without disabling 'Stop on Exception', the multicast still aborts remaining branches on error.
- ✗
Change the multicast to sequential processing and set the SFTP branch as the first route.
Why it's wrong here
Sequential processing determines the order in which branches run, not how errors are handled. Making the SFTP branch run first would actually cause the failure to occur earlier, and the default exception behavior would still stop the second branch. Ordering alone does not isolate the failure, so the email would still be skipped.
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.