Mule application property sources and providers
Where a Mule application's property values can come from (placeholders, global properties, properties files, system and environment properties, deployment properties, built-ins), which source wins, and when a custom configuration properties provider is the right tool.
Select among available options for setting Mule application properties.
~7 min read · 9 practice questions
What the exam expects
- Choose the right property source (global property, properties file, file property, system property, environment variable, deployment property) for a given requirement.
- Predict which value wins when the same property name is defined in several sources, and which built-in properties must be left alone.
- Set JVM system properties for a standalone Mule runtime from the command line or
wrapper.conf, including properties in included wrapper files. - Decide when a custom configuration properties provider fits and when a changing value needs a connector operation instead.
- Recognize how Mule discovers a custom provider factory, matches it to a configuration element and routes placeholders to it.
Property placeholder: an Ant-style ${name} reference in Mule configuration that Mule resolves from a property source. Configuration properties: values loaded from a .yaml or .properties file by <configuration-properties>. System property: a JDK property set when the Mule JVM starts. Deployment property: a value supplied at deployment, for example in Runtime Manager. Custom configuration properties provider: a Mule SDK module that resolves placeholders from a source you implement (Configuring Properties, Custom provider).
Key facts
- Detail
.yamland.properties;Stringis the only type
- Detail
src/main/resources, or an absolute path
- Detail
- The first definition is preserved
- Detail
- Deployment, system, environment, application, global
- Detail
app.home,app.name,domain.name,api.name,mule.home; never overwrite
- Detail
mule start -M-Dmule.<variable-name>=<value>
- Detail
- VM arguments field, names prefixed with
-D
- Detail
- High unique
<n>pluswrapper.ignore_sequence_gaps=TRUE
- Detail
- SPI, via
META-INF/services
- Detail
- Element namespace and name match
getSupportedComponentIdentifier()
- Detail
- A unique
PREFIX::in the placeholder
- Detail
- Connector operation, not a properties provider
- Why can a custom configuration properties provider not support connectivity testing?
- When you customize the sample custom-provider project, which class holds the
EXTENSION_NAMEconstant you rename? - What is the earliest Mule version the sample custom-provider project is compatible with?
- When the sample module's behavior changes, where do you add test cases for it?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Integration Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 40 lessons of the MuleSoft Platform Integration Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both