Deploying API implementations to CloudHub11% of the exam
CloudHub Worker Recovery and Reliability
Predict classic CloudHub workload distribution, queue and connection behavior, and the recovery dependencies that constrain updates and regional plans.
Given an app deployed to the CloudHub shared worker cloud in one or more regions, describe and predict its reliability and performance characteristics.
~7 min read · 7 practice questions
What the exam expects
- Predict which work additional CloudHub workers can distribute.
- Separate persistent-queue protection from exactly-once delivery.
- Interpret waiting, in-flight and processed queue evidence before operating on a queue.
- Account for idle connections, update limitations and unavailable deployment services.
Worker scale-out adds independent runtime instances; persistent queues retain queued work; in-flight messages are being processed after a queue; an idle timeout measures a period without data; a durable subscriber can impose an exclusive external identity (High availability, Queues, Networking, Runtime updates). This lesson uses classic CloudHub workers.
Key facts
HTTP distribution
- Detail
- Requests distribute across assigned workers.
- Source
- HA (opens in a new tab)
Batch distribution
- Detail
- One job runs on one worker at a time.
- Source
- HA (opens in a new tab)
Delivery semantics
- Detail
- Persistent queues can deliver duplicates.
HTTP-only workloads
- Detail
- Persistent queues are not required for load distribution.
- Source
- HA (opens in a new tab)
In-flight work
- Detail
- Remains on the queue until processing completes.
Clear
- Detail
- Flushes waiting and in-flight messages.
Idle timeout
- Detail
- 300 seconds without data closes both connections.
Durable subscriber
- Detail
- Exclusive identity can require manual stop/start for updates.
Recovery dependency
- Detail
- US East failure can block new deployments through the control plane.
- Why is disabling persistent-queue encryption unsafe to treat as a future-write-only change?
- When counts change before the throughput thumbnail refreshes, which cadence difference explains it?
- When batch should stop using persistent queues while other components retain them, which setting scopes that change?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 47 lessons of the MuleSoft Platform Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (7 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