Which statement describes how a Mule transaction can be rolled back?

• A. After a failure occurs in a transaction scope, but only if the error is not handled in an On Error Continue Scope
• B. Committed automatically at end of Flow
• C. On Error Propagate
• D. By throwing an error in a flow or in a Try scope using: raise-error

Answer: (A)

Mule transactions are atomic: they either commit if everything in the scope succeeds, or roll back when something goes wrong inside that scope. The rollback happens when a failure occurs within a transaction scope and the error is not handled by an On Error Continue scope. On Error Continue catches errors and allows the flow to keep executing, which means the transaction can complete and be committed. If you raise an error or let one propagate and it remains unhandled, the transaction is rolled back. So the described scenario—an failure inside a transaction that isn’t swallowed by On Error Continue—best explains how a rollback occurs.