Event-driven APIs with Anypoint MQ and JMS
Design event-driven integrations on two brokers: correlate asynchronous AsyncAPI replies, choose Anypoint MQ standard or FIFO queues, assign dead-letter queues with their encryption and delivery-attempt rules, and scale or filter JMS consumers with shared subscriptions and selectors.
Create high-level integration architectures using event-driven APIs and message brokers.
~8 min read · 8 practice questions
What the exam expects
- Keep the business identifier that lets a consumer match an asynchronous result to its request on shared AsyncAPI channels.
- Choose between Anypoint MQ standard and FIFO queues from ordering, delivery-guarantee and throughput requirements.
- Assign a dead-letter queue that satisfies Anypoint MQ's compatibility rules, and predict how it affects FIFO order, encryption and delivery counts.
- Scale a JMS topic subscription across consumers and filter a shared JMS destination at the source.
Message broker: a service that stores messages between publishers and subscribers, such as Anypoint MQ or a JMS provider. Dead-letter queue (DLQ): a queue that stores undeliverable messages from other queues. Message group: a set of FIFO messages processed in order by one consumer at a time. NACK: an operation in which the app does not take the message and Anypoint MQ does not delete it. JMS selector: a JMS selector-language expression that limits which messages a source receives (MQ glossary, JMS listener).
Sources for this section (2)
Key facts
- Detail
- At least once; occasional duplicates.
- Detail
- 300 TPS, or up to 3,000 msg/s batching 10 per operation; failed requests count.
- Detail
- Same type, region, environment and account.
- Detail
- Default 10; range 1-1000.
- Detail
- Message-group order not guaranteed.
- Detail
- Viewing counts toward maximum deliveries; returning is a NACK.
- Detail
- Body only, AES-256 GCM; headers and properties not encrypted.
- Detail
- Rerouted: source setting; direct publish: DLQ setting.
- Detail
- JMS 2.0 only; not with No local.
- Detail
- 4 consumers; ACK after successful flow completion.
- When does a change to a FIFO queue's delivery delay affect messages already in the queue?
- Why does Message Browser ask you to acknowledge a warning before retrieving messages from a FIFO queue?
- Which three settings make a Mule flow consume a FIFO message group strictly one message at a time?
- How many messages can a JMS On New Message source have in flight with default settings?
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 (8 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