How would we parameterize a configuration file in global.xml?

• A. Use a separate environment-specific properties file loaded via a bootstrap process
• B. Define the "configuration-properties" tag's "file" attribute as the parameterized configuration file name (e.g., "properties-${env}.yaml")
• C. Use the system property to switch files at runtime
• D. Specify a default properties file in the global.xml

Answer: (B)

Parameterizing the configuration file in global.xml focuses on externalizing configuration so the same application can run against different environments. By using the configuration-properties element's file attribute with a placeholder like properties-${env}.yaml, Mule resolves the env value at deploy or run time and loads the corresponding file. This approach lets you switch configurations without altering code or redeploying, which is exactly what parameterization aims for. The other options introduce extra bootstrap steps, rely on manual runtime switching, or lock you into a single default file, making environment-specific behavior harder to manage.