What happens when a system exception strategy is invoked?

• A. The exception is ignored and the flow continues
• B. The reconnection strategy is always ignored
• C. The exception is logged and the global default handles it
• D. It is non configurable, logs the exception, and if the exception was caused by a connection failure it executes the reconnection strategy

Answer: (D)

When a system-level error occurs, Mule uses a built-in, non-configurable path to handle it. This path is designed to provide a consistent response and is not something you typically customize within each flow. The system exception strategy logs the incident so you have a record for diagnostics. If the root cause is a connection failure to an external resource, it will trigger the reconnection strategy to attempt to re-establish the connection. This combination—not configurable, with logging, and conditional reconnection on connection failures—best describes how system exceptions are handled. The idea that the error would be ignored, or that reconnection is always ignored, or that a global default handles everything, doesn’t align with how system-level errors are managed in Mule.