Where are application properties typically defined and how are placeholders referenced?

Where are application properties typically defined and how are placeholders referenced?

• A. They are defined in App-dev.properties only
• B. They must be hard-coded into the source code
• C. They are usually placed in src/main/resources with db.port = 3306 and placeholders like ${db.account}
• D. They cannot reference placeholders

Answer: (C)

Externalized configuration is the idea here: application properties are kept in resource files so you can change behavior without rebuilding code. In MuleSoft projects, those properties are usually placed under the resources directory (src/main/resources), in a file such as app.properties, where you define key-value pairs like db.port=3306. You then reference these values in your Mule configuration using the placeholder syntax ${db.port}, which the runtime resolves to the actual value at startup. This setup keeps configuration separate from the application logic and makes it easy to switch values for different environments by providing different properties files or environment overrides. Hard-coding values breaks this flexibility, and placeholders are indeed designed to be referenced, so the approach described is the standard and correct one.

Externalized configuration is the idea here: application properties are kept in resource files so you can change behavior without rebuilding code. In MuleSoft projects, those properties are usually placed under the resources directory (src/main/resources), in a file such as app.properties, where you define key-value pairs like db.port=3306. You then reference these values in your Mule configuration using the placeholder syntax ${db.port}, which the runtime resolves to the actual value at startup. This setup keeps configuration separate from the application logic and makes it easy to switch values for different environments by providing different properties files or environment overrides. Hard-coding values breaks this flexibility, and placeholders are indeed designed to be referenced, so the approach described is the standard and correct one.