How are modules configured in a Mule application?

• A. Not required
• B. As a Maven dependency in pom.xml
• C. As a Maven artifact in the local repo
• D. As a module within the application

Answer: (B)

Modules in a Mule application are added by declaring them as Maven dependencies in the application's pom.xml. This approach lets the build system fetch the module as a packaged artifact and include it on the application's classpath, so the Mule runtime can load and expose the module’s features when the app runs.

Why this is the best fit: declaring a module as a Maven dependency is the standard, scalable way to bring in extendable functionality to a Mule app. It keeps module versions aligned with the runtime, supports transitive dependencies, and allows packaging the exact set of modules with the application.

The other options don’t fit as well. Not required is inaccurate because many scenarios rely on specific modules to use certain capabilities. Simply being a Maven artifact in the local repo describes where Maven stores artifacts, not how you configure them for a particular application. And treating a module as a component embedded directly inside the application ignores how Mule expects modules to be managed and loaded via the build configuration.