Implement performant and reliable Mule applications27% of the exam
Fault tolerance for HTTP API calls
Separate HTTP transport retries from flow retry scopes, preserve failure signals, and predict response, variable and completion behaviour at each boundary.
Implement fault-tolerant invocations of HTTP-based APIs, reacting correctly to HTTP status codes.
~6 min read · 6 practice questions ·
What the exam expects
- Separate transport retries, response classification and business-state polling.
- Place error propagation and fallback handling at the intended retry boundary.
- Predict variables across failed and successful attempts.
- Interpret synchronous execution, retry pacing and attempt logs correctly.
A response validator classifies a received status; a transport retry repeats a request after a transport failure; Until Successful retries a bounded processor scope; propagation exposes an error to its owner; exhaustion means the configured retries failed (HTTP retries, Until Successful).
Sources for this section (2)
Key facts
Request reconnection
- Detail
- SDK reconnection configuration does not govern HTTP Request retries.
Built-in disable control
- Detail
mule.http.client.maxRetries=0disables that mechanism.
Default classification
- Detail
- Received statuses 400 and above cause HTTP errors.
Redirect inspection
- Detail
- Follow Redirects governs whether the original redirect is exposed.
Business-state polling
- Detail
- A pending 200 needs a failure signal inside the retry scope.
Exhaustion
- Detail
- The final scope failure is
MULE:RETRY_EXHAUSTED.
Inner Continue
- Detail
- A handled owner completes successfully and can hide the retry signal.
Attempt state
- Detail
- Failed variable changes reset; successful output propagates.
Retry diagnostics
- Detail
- Attempt-level ERROR logs can precede later success.
- Why does the following processor wait while Until Successful retries?
- When attempt timestamps are uneven, why inspect attempt duration before blaming the interval configuration?
- Does one ERROR-level router retry entry establish the final business outcome?
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 (6 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