C_CPI Integration Suite Development Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use an HTTPS sender adapter and have an external scheduler call the endpoint every weekday at 06:00 using a client certificate.

  Why it's wrong here

  Introducing an external scheduler and HTTPS sender shifts the scheduling responsibility outside the tenant and requires certificate management plus network exposure. It also removes the self-contained Timer behavior that Cloud Integration provides natively. While it can work, it adds infrastructure and security overhead that the built-in Timer schedule avoids entirely.

• ✗

  Deploy five separate integration flows, each with a Timer Start event scheduled once per week on a single weekday at 06:00.

  Why it's wrong here

  Five flows duplicate the same integration logic and multiply deployment, monitoring, and maintenance effort. Each flow also consumes its own message processing capacity, which is heavier than a single scheduled flow. A cron expression on one Timer already provides the weekday restriction, so this approach adds unnecessary operational overhead.

• ✓

  Configure the Timer Start event with Schedule to 'Run on Schedule', a recurrence of Daily, and enter a cron expression that restricts execution to Monday through Friday at 06:00.

  Why this is correct

  The Timer Start event supports a cron expression when Schedule is set to Run on Schedule, letting you encode a Monday-through-Friday window at 06:00 in a single trigger definition. SAP Cloud Integration evaluates the cron in the tenant time zone, so weekends are excluded without any extra flow steps, minimizing runtime overhead.

• ✗

  Set the Timer Start event to Schedule to 'Run Once', then add a Router step that checks the current day name and stops processing on weekends.

  Why it's wrong here

  A Run Once timer fires a single time after deployment and then never again, so the flow would not repeat daily at 06:00. Adding a Router that stops weekend processing does not create the daily schedule, so the flow would still fail to trigger on weekdays. This configuration cannot satisfy the recurring weekday requirement.