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.

• ✗

  Add a Retry step from the palette after the OData V2 receiver adapter.

  Why it's wrong here

  There is no dedicated 'Retry' step in the SAP Cloud Integration palette. Retry logic is typically configured within adapters or implemented using exception subprocesses and loops. Adding a non-existent step would not be possible. Even if a loop were used, it would not automatically catch adapter-level errors without additional error handling, making this approach incorrect.

• ✓

  Configure the retry settings in the OData V2 receiver adapter.

  Why this is correct

  The OData V2 receiver adapter in SAP Cloud Integration provides built-in retry configuration, including maximum retries and retry interval. Setting these values directly in the adapter is the simplest and most appropriate way to handle transient errors from the S/4HANA system, as it applies specifically to that adapter's outbound calls without additional flow logic.

• ✗

  Configure the retry settings in the Integration Flow's runtime configuration under 'Error Handling'.

  Why it's wrong here

  SAP Cloud Integration does not have a global 'Error Handling' section in the integration flow runtime configuration that provides per-adapter retry settings. Error handling is typically done via exception subprocesses or adapter-specific settings. The OData V2 receiver adapter itself contains the retry parameters, so looking elsewhere would not achieve the required behavior.

• ✗

  Use a Loop step with a counter and a Timer to retry the message three times.

  Why it's wrong here

  While a Loop step could theoretically implement retries, it would require complex configuration with exception handling to catch errors from the OData adapter. The adapter's built-in retry is far simpler and more reliable. A Loop step does not automatically retry on adapter errors; it would continue regardless of success or failure unless explicitly programmed, which is not the intended use here.