What does Single-resource TX refer to in Mule transactions?

• A. Local transactions that apply when there is only one database in try scope
• B. Global distributed
• C. It doesn't exist
• D. It's the same as two-phase commit

Answer: (A)

Single-resource TX is about coordinating a transaction when only one transactional resource participates. In Mule, a transaction can involve multiple resources, but if there’s just one resource in the try scope, Mule uses a local transaction on that resource. This means the resource’s own transactional behavior (for example, a single JDBC connection’s commit/rollback) governs the operation, with no distributed coordination. That’s why it’s described as local transactions that apply when there is only one database in the try scope.

If you add more than one transactional resource, Mule would move toward a distributed/XA-style transaction that coordinates across resources (often involving a two-phase commit). The option that says it’s globally distributed, or that it doesn’t exist, or that it’s the same as two-phase commit, doesn’t fit because those describe multi-resource coordination, not the single-resource case.