When creating global exception strategies, which approach allows them to be invoked from within a global strategy?

• A. Use a standard exception strategy
• B. Use reference exception strategy to call global strategies
• C. Call them directly by name within the global strategy
• D. Global exception strategies cannot be invoked

Answer: (B)

The idea being tested is how to reuse and compose error handling across parts of an integration. In MuleSoft, a global exception strategy is a reusable plan for handling errors. If you want one global strategy to invoke another, you use a Reference Exception Strategy that points to the named global exception strategy. This creates a clean, modular way to compose exception handling: one global strategy calls another through that reference, enabling reuse and consistent behavior across flows.

Using a standard exception strategy isn’t designed for invoking another global strategy from within a global context, so it wouldn’t provide the same modularity. Calling a global exception strategy directly by name isn’t how the runtime wires such calls inside a global strategy, and saying global exception strategies cannot be invoked is incorrect.