Q: 2
Which SAP Cloud Integration process event allows you to run integration flows directly after
deployment?
Options
Discussion
D . Timer event is the only one that can fire the iFlow right after deployment without needing a message to be sent in or manual action. Router and Content Modifier just handle logic within the flow, they don't trigger it. Pretty sure that's what SAP means by "run directly after deployment." Happy to hear another take though.
Option D works here. Timer lets the iFlow start itself as soon as you deploy, no need for manual input. Saw a similar question on a practice set, pretty sure that's what SAP expects. Anyone disagree?
I don't think it's D. B. Router sounds like it could handle messages right after deployment, especially if you send one in quickly. Official SAP guide examples sometimes start flows this way, but could be reading it wrong.
Yeah, it's D here. Timer with 'Run Once' is the event that auto-triggers the iFlow as soon as you deploy it, no message required. Router (B) only processes incoming messages after the flow starts, can't actually start it itself. I think that's what SAP is looking for, but open to other views.
Seen this in a couple practice exams and the SAP official guide. D is usually correct for triggering flows post-deployment.
I don’t think B fits, D is correct. Timer lets you automate iFlow execution right after deployment. SAP doc and some practice tests confirm this, definitely check the official guide for these event triggers.
D . Timer is the only one that can auto-trigger execution on deployment, Router (B) just handles flow decisions once the process is running. Pretty sure that's what SAP wants here, but open if someone has evidence for B.
Why not B here? Router handles control in the flow and could take action as soon as a message comes through post-deploy, right?
It’s D, Timer is the only event that can auto-trigger an integration flow immediately after deployment. Router (B) is tempting, but it just handles logic once the flow is already started, it can’t initiate the iFlow. I’ve seen similar questions where Timer with 'Run Once' is what SAP means here. Let me know if you see it differently!
Why do some think Router (B) can trigger right after deployment? Isn't it only for branching logic once a flow is actually started, not for kicking off the flow itself?
Be respectful. No spam.
