A Mule application is configured to dynamically accept the package name it needs to log, as well as the package's level, during startup. What are the two required steps?

• A. Install a new logging plugin; restart with default settings.
• B. Change the application code to read system properties at startup; deploy to production.
• C. Add an AsyncLogger in log4j2.xml in the Configuration > Loggers scope; start the Mule server with -Dlog.package and -Dlog.level.
• D. Enable all loggers; export LOG_PACKAGE and LOG_LEVEL environment variables.

Answer: (C)

The idea being tested is how to dynamically configure per-package logging at startup using the logging framework and startup properties. In Mule, log4j2 is the logging backbone, so you control how a specific package logs by defining a dedicated logger for that package in the log4j2.xml under the Configuration > Loggers section, using an AsyncLogger to handle log events efficiently. Then you supply the package name and the desired log level at startup via system properties (-Dlog.package and -Dlog.level); Mule reads these properties at startup and applies them to the logger you defined, enabling you to tailor logging without code changes or redeploys. This combination lets you choose which package to log and at what level on startup, which is exactly what dynamic startup logging requires. Other approaches—like installing plugins, changing application code, enabling all loggers, or relying on environment variables with nonstandard names—don’t provide the same targeted, runtime-controlled behavior.