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.

• ✗

  None

  Why it's wrong here

  Setting the transaction mode to 'None' means no transactional guarantees are applied; the message is consumed and removed from the queue without waiting for successful processing. This is similar to auto-commit but with even less overhead, and it definitely does not protect against message loss if the integration flow fails. It is used only when message loss is acceptable, which contradicts the scenario requirement.

• ✗

  Auto-commit

  Why it's wrong here

  Auto-commit mode commits the message as soon as it is read from the queue, before the integration flow completes processing. If the flow fails after reading, the message is already removed and cannot be redelivered, leading to data loss. This mode is suitable for non-critical messages where loss is acceptable, but it does not meet the requirement of ensuring messages are not lost on failure.

• ✗

  Client-acknowledged

  Why it's wrong here

  Client-acknowledged mode is not a standard option for the JMS sender adapter in SAP Cloud Integration. The adapter typically offers Auto-commit, Transacted, and None. Even if it were available, it would require manual acknowledgment, which is not supported by the integration flow engine automatically. Therefore, it is not the correct configuration to ensure no message loss in this context.

• ✓

  Transacted

  Why this is correct

  Transacted mode in SAP Cloud Integration JMS adapter ensures that the message is only acknowledged (committed) after the integration flow completes successfully. If the flow fails, the transaction is rolled back and the message remains in the queue for redelivery. This provides exactly-once or at-least-once delivery semantics, preventing message loss. It is the correct choice when messages must not be lost on processing failure.