Which statement about configuring Bitronix as the XA transaction manager is correct?

• A. You declare it as a global configuration element in the Mule application
• B. It can be used in multiple Mule domains at the same time
• C. It requires a separate runtime instance per application
• D. It cannot be used in customer-hosted deployments

Answer: (A)

In Mule, the XA transaction manager is configured at the application level by declaring Bitronix as a global configuration element. This approach creates a single, shared transaction manager instance that all components and flows within that Mule application can use to coordinate distributed transactions across resources like databases or message queues. It ensures a consistent transactional context for XA operations within the runtime hosting that application.

This fits because a transaction manager is a runtime-wide resource tied to a specific Mule runtime environment; it isn’t intended to be set up per domain or per individual application. Typically, a single runtime instance (which can host multiple applications) provides the TM for all of them, and it can be used in customer-hosted deployments as well. The other options describe scenarios (sharing across domains, requiring a separate runtime per application, or being unusable in customer deployments) that aren’t how Bitronix is configured in Mule.