Mule Dev 201 study plan · 8 min read

How to prepare for the MuleSoft Developer I exam

By the MulePrep team · Updated June 2026

To prepare for the MuleSoft Developer I exam, plan on a few weeks of steady, hands-on study in Anypoint Studio rather than a weekend of reading. This guide gives you a week-by-week plan mapped to the official topic areas, the concepts that carry the most weight, and how to practice with timed questions so the knowledge holds up under exam pressure. There is no shortcut and no pass guarantee, but a focused plan removes most of the guesswork.

What the Developer I exam actually tests

The exam is officially the Salesforce Certified MuleSoft Developer I, sometimes still called MCD Level 1. It checks whether you can design, build, test, debug, deploy, and manage basic APIs and integrations using Mule 4 and Anypoint Studio. The format is consistent across the MuleSoft developer and architect exams:

• 60 multiple-choice questions in a single sitting.
• 120 minutes total, which works out to two minutes per question.
• 70 percent to pass - that is 42 of 60 questions correct.
• Closed book. You cannot open documentation or your own notes during the exam.
• Online-proctored or test-center, your choice when you register.
• Valid for two years from the date you pass.

The questions lean practical. Many describe a small flow or a DataWeave snippet and ask what it produces, why it fails, or which component fits. That is why reading alone rarely gets people over the line - the exam is built around what you have actually done in Studio.

For the current fee, registration steps, and any policy changes, check the official credential page directly, since these are updated independently of study material. As of June 2026 the Developer I exam fee is listed at USD 200, with a lower retake fee, but treat the official page as the source of truth: Salesforce Certified MuleSoft Developer I credential page.

How long it takes to prepare

The honest answer to how long to study for MCD Level 1 is: it depends almost entirely on your existing Mule 4 experience. There is no fixed number of hours that guarantees a pass.

• Daily Mule 4 work: two focused weeks is often enough to fill gaps and get used to the question style.
• Some integration background, new to Mule: three to four weeks of consistent evenings.
• New to Anypoint Studio and DataWeave: four to six weeks, with most of the time spent building rather than reading.

Consistency beats intensity. An hour a day for a month sticks far better than two long weekends of cramming, because the exam rewards recall under time pressure - something only spaced, repeated practice builds. The plan below assumes limited Mule 4 experience; compress it if you already work in the platform.

A 4-week study plan

This is a MuleSoft Certified Developer Level 1 study plan built around the official topic areas, ending in timed practice. Each week has a build goal, because hands-on repetition is what the exam measures. Treat the weeks as phases, not strict calendar boxes - move on only when the build goal feels comfortable.

Week 1 - Fundamentals and your first flows

Install Anypoint Studio and get comfortable with the canvas, the palette, and the Mule event structure (attributes, payload, variables). Build a few simple flows with an HTTP Listener, a Logger, and a Set Payload. Learn how a RAML-defined API maps to a flow via APIkit, and how Anypoint Platform pieces fit together at a high level.

• Build: a small HTTP API that returns a static JSON response.
• Understand: the Mule event - how payload, attributes, and variables move through a flow.
• Read: the Anypoint Studio interface and the anatomy of a Mule application.

Week 2 - DataWeave

DataWeave 2.0 is the single most important skill on this exam, so give it a full week. Practice mapping between JSON, XML, and Java. Learn the core operators and functions you will see repeatedly: map, filter, reduce, pluck, groupBy, orderBy, and selectors. Type a transformation, predict the output, then run it and compare.

• Build: a transformation that reshapes an array of records into a grouped summary.
• Understand: the difference between map and mapObject, and how selectors handle missing keys.
• Practice: reading a snippet and predicting its output without running it - the exam will ask exactly this.

Week 3 - Error handling and flow control

Spend this week on two areas that trip people up: error handling and routing. For error handling, learn how On Error Continue and On Error Propagate differ, how error scopes nest, and how error types are matched. For flow control, work through Choice, Scatter-Gather, For Each, and the difference between a Flow, a Sub Flow, and a Private Flow.

• Build: a flow with a Try scope and both error handlers, then observe how each changes the outcome.
• Understand: when a propagated error re-enters the calling flow versus when it is handled and continues.
• Review: Choice routing conditions and how Scatter-Gather aggregates results.

Week 4 - Connectors, deployment, and timed practice

Round out coverage with database and file connectors, consuming a REST API with the HTTP Request connector, and processing records. Then deploy an app to CloudHub and practice debugging with breakpoints and the Mule debugger. Spend the back half of the week on full-length, timed practice under exam conditions.

• Build: a flow that reads from a connector, transforms with DataWeave, and handles errors end to end.
• Deploy: push a small app to CloudHub and read its logs.
• Simulate: sit a timed 60-question set and review every miss the same day.

The topics worth the most points

Not every MuleSoft Developer 1 exam topic carries equal weight. If you are short on time, concentrate where the questions cluster. The published topic areas span the full development lifecycle, but in practice these five reward your study hours the most.

DataWeave and error handling deserve special attention because their questions are precise: a single wrong assumption about how a selector handles a missing key, or whether a handler swallows an error, flips the answer. These are also the areas where hands-on practice pays off fastest.

How to practice so it sticks

Reading explanations feels productive, but recall under a clock is a different skill - and that is exactly what the exam measures. Build your practice around three habits.

Practice with timed questions

Do questions against a clock from early on, not just at the end. Two minutes per question is comfortable until a long DataWeave snippet eats your time. Practising timed teaches you to flag a hard question, move on, and come back - a skill that protects easy points you would otherwise lose to the clock.

Learn from every explanation

A correct guess teaches you nothing. After each question, read why the right answer is right and why the others are wrong. The wrong options on a well-written question usually encode a common misconception, so understanding them closes gaps you did not know you had.

Redo your misses

Keep a list of every question you got wrong and revisit it a few days later. Spaced repetition of your specific weak spots is the most efficient revision there is. If you miss the same concept twice, go back to Studio and build a small flow that demonstrates it rather than re-reading the explanation a third time.

Exam-day logistics

When you register, you choose between an online-proctored exam from home or a physical test center. Both use the same 60 questions, 120-minute limit, and 70 percent passing bar.

If you take it online

• You need a quiet, private room with no one else present, a clear desk, a working webcam, and a stable internet connection.
• A proctor verifies your ID and watches via webcam, so check in early to allow time for the system and environment checks.
• You cannot use notes, a second monitor, your phone, or any documentation - it is closed book.

If you take it at a test center

• Bring valid photo ID and arrive ahead of your slot.
• The center provides the machine; personal items go in a locker.

Either way, your result is shown shortly after you submit. If you do not pass, you can register again after the required wait, usually at a reduced retake fee - confirm the current retake policy and fee on the official credential page before you rebook.