How is a properties file named training-DEV.properties referenced in the Mule application?

How is a properties file named training-DEV.properties referenced in the Mule application?

• A. In a MEL expression
• B. In a Configuration element
• C. In a DataWeave script
• D. In a Property Placeholder element

Answer: (D)

Loading external configuration is done with a Property Placeholder element. This element points to the external properties file (for example, classpath:training-DEV.properties) and reads its key-value pairs, making them available in the Mule configuration as ${propertyName}. This lets you parameterize your flows and components without hard-coding values, so the same app can run in different environments by swapping the properties file. The other options don’t serve this purpose: MEL expressions evaluate runtime logic, DataWeave handles data transformation, and a Configuration element by itself doesn’t load external properties.

Loading external configuration is done with a Property Placeholder element. This element points to the external properties file (for example, classpath:training-DEV.properties) and reads its key-value pairs, making them available in the Mule configuration as ${propertyName}. This lets you parameterize your flows and components without hard-coding values, so the same app can run in different environments by swapping the properties file.

The other options don’t serve this purpose: MEL expressions evaluate runtime logic, DataWeave handles data transformation, and a Configuration element by itself doesn’t load external properties.