What the published objective requires
- Select expressions for payload, attributes and variables
- Predict state after event processors
- Preserve the current event while enriching it with connector targets
Domain 3 of 12 · 10% of the official blueprint
Accessing and Modifying Mule Events practice lesson
Predict payload, attribute and variable state across the complete Northstar flow.
The misconception to eliminate
Treating payload, attributes and variables as one mutable map. They have different lifecycles and purposes.
Practice allocation: 6 of 60 questions in our whole-question mock blueprint.
Decision rules
Retrieve these without looking before attempting the question.
Rule 1
The Mule message contains payload and attributes; variables are event metadata.
Rule 2
Transport metadata is connector-specific attributes—HTTP query parameters are not payload fields.
Rule 3
Each event modification produces a new event; reason about the state at the current processor.
Rule 4
A connector target captures operation output in a variable and preserves the current payload.
Worked Northstar scenario
Scenario
The order payload must survive while a CRM lookup returns a customer record.
Reasoning
Set customerId from payload if needed, execute HTTP Request with target=customer, then combine payload and vars.customer in DataWeave. Do not replace the payload and rebuild it later.
Free practice question
After an HTTP Listener, where is the request method normally found?
- payload.method
- vars.method
- attributes.method
- error.method
Reveal answer and reasoning
Answer: C. HTTP transport metadata is exposed through the listener attributes.
The complete program contains five guided drills for this domain, an 80% mastery gate, saved progress and a separate 60-question timed mock.
Get Domain MasteryHands-on proof preview
Trace the event ledger
Predict state at four processors before running the flow.
- Write payload, attributes and vars immediately after the HTTP Listener.
- Predict state after Set Variable customerId.
- Configure the CRM request with target customer.
- Run and verify the order payload is unchanged while vars.customer contains the response.
Evidence to keep: A four-row event ledger whose predicted values match the debugger for payload, attributes and two variables.
Primary sources
Questions about this domain
How much of the MuleSoft Developer exam is Accessing and Modifying Mule Events?
Salesforce publishes a weight of 10% for this domain. In a 60-question practice allocation, that is represented here by 6 questions.
Is this Accessing and Modifying Mule Events question from the real exam?
No. It is original independent practice material written only from public exam objectives and product documentation.