What practice helps avoid hard-coding credentials in MuleSoft applications?

What practice helps avoid hard-coding credentials in MuleSoft applications?

• A. Storing credentials directly in code
• B. Use a separate credentials service that is polled on each request
• C. Injecting credentials at runtime via application properties
• D. Store credentials in a publicly accessible Git repository

Answer: (C)

Externalizing credentials and resolving them at runtime through application properties keeps secrets out of the code and makes them environment-specific. In MuleSoft, you reference values with placeholders like ${db.password} in your configuration and supply the actual value in a properties file such as mule-app.properties (or via environment variables or secure properties). This approach allows the same application to run in different environments with different credentials, and it makes it much easier to rotate secrets without touching the code. It’s more secure and maintainable than embedding credentials directly in code, which would expose them in version control. Using a centralized credentials service on every request adds unnecessary complexity and potential latency, while storing credentials in a publicly accessible Git repository is a clear security risk.

Externalizing credentials and resolving them at runtime through application properties keeps secrets out of the code and makes them environment-specific. In MuleSoft, you reference values with placeholders like ${db.password} in your configuration and supply the actual value in a properties file such as mule-app.properties (or via environment variables or secure properties). This approach allows the same application to run in different environments with different credentials, and it makes it much easier to rotate secrets without touching the code. It’s more secure and maintainable than embedding credentials directly in code, which would expose them in version control. Using a centralized credentials service on every request adds unnecessary complexity and potential latency, while storing credentials in a publicly accessible Git repository is a clear security risk.