Implement performant and reliable Mule applications27% of the exam
Reliable messaging with VM and Anypoint MQ
Configure VM delivery controls and Anypoint MQ settlement, preserve broker evidence, and publish distinct business events and routing metadata deliberately.
Implement fault-tolerant, performant, and traceable message passing with the VM and AnypointMQ connectors.
~6 min read · 18 practice questions ·
What the exam expects
- Configure VM consumption, transactions and redelivery identity separately.
- Choose MQ consumption and acknowledgement boundaries for the processing contract.
- Preserve broker traceability and publish identity without conflating business events.
- Publish body content, media type and user properties deliberately.
A consumer pulls queued work into a flow; redelivery repeats broker delivery; ACK settles a message; NACK returns it for delivery; message ID identifies the published message; user properties carry application-defined metadata (VM reference, MQ acknowledgements, Publication).
Key facts
VM capacity
- Detail
- Number Of Consumers controls concurrent queue consumption.
- Source
- VM (opens in a new tab)
VM transaction start
- Detail
- Listener
ALWAYS_BEGINstarts the source transaction. - Source
- VM (opens in a new tab)
Redelivery identity
- Detail
- Java payloads use
hashCode()unless an explicit ID strategy is selected.
Consume destination
- Detail
- Anypoint MQ Consume reads queues, not exchanges.
AUTO settlement
- Detail
- Successful Subscriber flow completes acknowledgement.
- Source
- ACK (opens in a new tab)
MANUAL settlement
- Detail
- Application logic retains and uses
ackToken. - Source
- ACK (opens in a new tab)
Failure settlement
- Detail
- NACK returns a message for redelivery.
- Source
- ACK (opens in a new tab)
Publish body
- Detail
- Defaults to the incoming payload serialized as a string.
FIFO retry identity
- Detail
- Reuse the same business-event ID for that event's publish retry.
Media type
- Detail
- Send Content Type publishes the body's media type property.
- Why can a body field be present while broker property routing still lacks its input?
- When a routing rule compares a numeric user property, why is the value's type relevant?
- Where can you inspect the user properties actually published with an MQ message?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Developer II pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 29 lessons of the MuleSoft Developer II guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (18 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