Default exception Strategy characteristics

Default exception Strategy characteristics

• A. It can be configured per flow
• B. It is customizable and replaceable
• C. It implicitly and globally handles all messaging exceptions, stops execution, CANNOT be configured, CAN be replaced with a Global Default exception strategy
• D. It applies only to JMS connectors

Answer: (C)

Default exception strategy is the global catch‑all for exceptions that aren’t handled by a flow’s own exception strategy. It applies implicitly across the application to all messaging exceptions, and when an exception reaches it, the current message processing stops and the default handling path takes over. You don’t configure this per flow; instead, you can replace it with a custom Global Default exception strategy to tailor behavior across the whole application. It’s not limited to JMS; it applies to messaging exceptions in general.

Default exception strategy is the global catch‑all for exceptions that aren’t handled by a flow’s own exception strategy. It applies implicitly across the application to all messaging exceptions, and when an exception reaches it, the current message processing stops and the default handling path takes over. You don’t configure this per flow; instead, you can replace it with a custom Global Default exception strategy to tailor behavior across the whole application. It’s not limited to JMS; it applies to messaging exceptions in general.