MuleSoft Developer 2 Certification Practice Exam

Externalizing environment-specific values and loading them in global.xml using a property placeholder is what this item is about. The format properties-${env}.yaml signals that the file is meant to supply key-value properties for different environments, with ${env} letting you substitute the target environment (such as dev, test, or prod) at deployment time. The prefix properties- clearly identifies the file as a properties-style source for configuration, and the YAML extension indicates the file uses YAML syntax for those properties, which is a common choice in newer Mule projects. Global.xml would reference values from this file to resolve ${...} placeholders across the configuration, enabling consistent environment-specific deployments. The other options don’t follow this established naming pattern for environment-specific property files used by parameterized configuration.