Mule-Dev-201 study guide · 2026

The 12 Mule-Dev-201 domains, explained

12 domains and 40 official objectives. Accessing and Modifying Mule Events carries the most weight at 10%. Each guide explains what the domain covers, how its questions are framed and where candidates lose marks.

Start with Domain 3 See all domains
Questions
60 multiple-choice questions (plus up to 5 unscored questions)
Time
120 minutes
Passing score
70%
Outline
Salesforce Certified MuleSoft Developer Exam Guide (Salesforce Help article 005298959; questions aligned to the Spring '24 release; 12 sections, 40 objectives) (current)

Exam blueprint

Bar widths follow the official weights. Weight ranges are drawn at their midpoint.

  1. 1 7%
  2. 2 8%
  3. 3 10%
  4. 4 10%
  5. 5 7%
  6. 6 10%
  7. 7 10%
  8. 8 10%
  9. 9 8%
  10. 10 8%
  11. 11 5%
  12. 12 7%
  1. 1 Creating Application Networks
  2. 2 Designing APIs
  3. 3 Accessing and Modifying Mule Events
  4. 4 Structuring Mule Applications
  5. 5 Building API Implementation Interfaces
  6. 6 Using Connectors
  7. 7 Processing Records
  8. 8 Transforming Data
  9. 9 Routing Events
  10. 10 Handling Errors
  11. 11 Debugging and Troubleshooting Mule Applications
  12. 12 Deploying and Managing APIs and Integrations

All 12 domains

40 official objectives 66–89 hrs suggested study

  1. Domain 01 7%

    Creating Application Networks

    The opening section tests why MuleSoft argues for reusable APIs: application networks, the three API-led layers, the Center for Enablement, and calling a RAML-described REST service from a Mule 4 flow.

    Inside this domain

    • Identify core architectural concepts of the Application Network and modern APIs.
    • Identify features of an API-led approach.
    • Identify features of MuleSoft's recommended Operational Model (C4E).
    • Apply correct processors / syntax and predict outcomes to consume RESTful web services (RAML-based) and predict outcomes.

    Watch for One API for everything

    Objectives
    4
    Questions est.
    ~4
    Study time est.
    4–6 hrs
  2. Domain 02 8%

    Designing APIs

    Designing APIs checks that you can read and write RAML 1.0: resources, nested resources, methods, parameters, request bodies and responses, and the choice between a query parameter and a URI parameter.

    Inside this domain

    • Use REST API methods and resources.
    • Define REST API parameters and responses.
    • Identify when and how to define query parameters vs URI parameters.

    Watch for Filter in the path

    Objectives
    3
    Questions est.
    ~5
    Study time est.
    5–7 hrs
  3. Domain 03 10%

    Accessing and Modifying Mule Events

    This section is about the Mule 4 event: what is in the message and what is in variables, which processors change each part, and how a connector target stores a result without replacing the payload.

    Inside this domain

    • Apply correct processors/DataWeave expressions to access and modify Mule event payloads, and predict outcomes.
    • Apply correct processors/DataWeave expressions to access and modify Mule event attributes, and predict outcomes.
    • Apply correct processors/DataWeave expressions to access and modify Mule variables, and predict outcomes.
    • Apply correct processors/DataWeave expressions to enrich Mule events using Mule 4 connector targets, and predict outcomes.

    Watch for Logger transforms

    Objectives
    4
    Questions est.
    ~6
    Study time est.
    7–9 hrs
  4. Domain 04 10%

    Structuring Mule Applications

    Structuring Mule Applications tests how you split an application into configuration and properties files, and how events move between flows, private flows and subflows through Flow Reference and connector boundaries such as VM.

    Inside this domain

    • Specify when and how to structure Mule applications into separate configuration and properties files, and predict outcomes.
    • Specify when and how to pass events between flows and subflows using connectors and flow references, and predict outcomes.

    Watch for Variables cross VM

    Objectives
    2
    Questions est.
    ~6
    Study time est.
    6–8 hrs
  5. Domain 05 7%

    Building API Implementation Interfaces

    This section is about the implementation side of an API: building interface flows by hand with HTTP Listeners, generating them with APIkit from RAML, and returning the status codes and bodies the specification promises.

    Inside this domain

    • Manually build API implementations from an API specification, RAML or not.
    • Predict the results of APIkit based upon a RAML specification.
    • Implement correct responses based on a RAML specification, either manually or with APIkit.

    Watch for 405 vs 404

    Objectives
    3
    Questions est.
    ~4
    Study time est.
    5–7 hrs
  6. Domain 06 10%

    Using Connectors

    Using Connectors covers the Database connector with parameterized SQL, the File and FTP connectors for reading, writing and listing files, and patterns for retrieving data in the middle of a flow and combining it with the current payload.

    Inside this domain

    • Apply correct processors/syntax to connect to databases, and predict outcomes.
    • Apply correct processors/syntax to connect to files or FTP servers, and predict outcomes.
    • Apply correct processors/syntax to retrieve and combine data in the middle of a flow, and predict outcomes.

    Watch for Single row object

    Objectives
    3
    Questions est.
    ~6
    Study time est.
    6–8 hrs
  7. Domain 07 10%

    Processing Records

    Processing Records tests how Mule handles collections: the For Each scope, Batch Jobs with steps and aggregators, database listeners that pick up new rows, and the Object Store for keeping data between flow executions.

    Inside this domain

    • Apply correct processors/syntax to process individual records in a collection using For Each scopes, and predict outcomes.
    • Apply correct processors/syntax to process individual records in a collection using batch scopes, and predict outcomes.
    • Apply correct processors/syntax to process individual records in a collection using DB listeners, and predict outcomes.
    • Apply correct processors/syntax to persist data between flow executions.

    Watch for Loop output

    Objectives
    4
    Questions est.
    ~6
    Study time est.
    7–9 hrs
  8. Domain 08 10%

    Transforming Data

    Transforming Data is the DataWeave section: converting JSON, XML, CSV and Java, predicting core function results, coercing and formatting values, calling flows with lookup, and packaging reusable functions in modules.

    Inside this domain

    • Convert between output types and data types using DataWeave.
    • Predict the result of core DataWeave functions.
    • Apply correct syntax to write DataWeave transformations to coerce, format, order, and filter data, and predict outcomes.
    • Call Mule flows from a DataWeave script.
    • and 1 more objectives

    Watch for Descending by default

    Objectives
    5
    Questions est.
    ~6
    Study time est.
    8–10 hrs
  9. Domain 09 8%

    Routing Events

    Routing Events covers three tools: the Choice router driven by DataWeave conditions, Scatter-Gather for sending one event down several routes at once, and the Validation module for rejecting events that do not meet rules.

    Inside this domain

    • Apply correct processors/syntax to route messages using DataWeave conditions within a choice router, and predict outcomes.
    • Apply correct processors/syntax to scatter and gather messages, and predict outcomes.
    • Apply correct processors/syntax to validate Mule events, and predict outcomes.

    Watch for Multiple matches

    Objectives
    3
    Questions est.
    ~5
    Study time est.
    4–6 hrs
  10. Domain 10 8%

    Handling Errors

    Handling Errors tests the Mule 4 error model: what the default handler does, global error handlers, On Error Continue versus On Error Propagate, combining handlers, Try scopes and mapping connector errors to custom types.

    Inside this domain

    • Apply correct processors/syntax to implement global error handlers, and predict outcomes.
    • Apply correct processors/syntax to implement on-error continue and on-error propagate handlers, and predict outcomes.
    • Apply correct processors/syntax to combine multiple error handlers, and predict outcomes.
    • Apply correct processors /syntax to implement try scopes, and predict outcomes.
    • and 1 more objectives

    Watch for Resume after failure

    Objectives
    5
    Questions est.
    ~5
    Study time est.
    6–8 hrs
  11. Domain 11 5%

    Debugging and Troubleshooting Mule Applications

    The smallest section has one objective: identify the root cause of errors when debugging Mule applications. Expect breakpoints and the Studio debugger, log messages, error types and the usual causes such as missing dependencies or ports.

    Inside this domain

    • Identify root causes for errors when debugging Mule applications, and predict outcomes.

    Watch for Status as cause

    Objectives
    1
    Questions est.
    ~3
    Study time est.
    3–4 hrs
  12. Domain 12 7%

    Deploying and Managing APIs and Integrations

    The final section moves from Studio to Anypoint Platform: deploying applications to CloudHub, placing APIs under API Manager with a proxy or autodiscovery, and applying policies such as client ID enforcement and SLA-based rate limiting.

    Inside this domain

    • Deploy applications to CloudHub.
    • Manage APIs using separate proxies and auto-discovery.
    • Manage API policies.

    Watch for Rebuild per environment

    Objectives
    3
    Questions est.
    ~4
    Study time est.
    5–7 hrs

Study the heaviest domains first

Marks follow weight. This order puts the most marks behind you first, across about 66–89 hrs of study.

  1. 3 Accessing and Modifying Mule Events 10% · 7–9 hrs
  2. 4 Structuring Mule Applications 10% · 6–8 hrs
  3. 6 Using Connectors 10% · 6–8 hrs
  4. 7 Processing Records 10% · 7–9 hrs
  5. 8 Transforming Data 10% · 8–10 hrs
  6. 2 Designing APIs 8% · 5–7 hrs
  7. 9 Routing Events 8% · 4–6 hrs
  8. 10 Handling Errors 8% · 6–8 hrs
  9. 1 Creating Application Networks 7% · 4–6 hrs
  10. 5 Building API Implementation Interfaces 7% · 5–7 hrs
  11. 12 Deploying and Managing APIs and Integrations 7% · 5–7 hrs
  12. 11 Debugging and Troubleshooting Mule Applications 5% · 3–4 hrs

Try one

Practice questionDomain 3: Accessing and Modifying Mule Events

A flow receives GET /orders?status=open. It sets vars.status to attributes.queryParams.status, then calls an HTTP Request to an inventory API with no target. A Logger then evaluates #[(attributes.queryParams.status default 'missing') ++ '-' ++ vars.status]. The inventory call returns 200. What does the Logger print?

One trap from every domain

The answer that looks right, and the clue that gives it away.

  • Domain 1

    One API for everything

    Clue The stem mentions future channels or other teams needing the same data.

  • Domain 2

    Filter in the path

    Clue Words like filter, search, sort or page.

  • Domain 3

    Logger transforms

    Clue The final question asks what the next processor receives.

  • Domain 4

    Variables cross VM

    Clue VM Publish or Publish Consume sits between the two flows.

  • Domain 5

    405 vs 404

    Clue The path matches the RAML but the verb does not.

  • Domain 6

    Single row object

    Clue The question says the query returns exactly one row.

  • Domain 7

    Loop output

    Clue A Logger right after the scope.

  • Domain 8

    Descending by default

    Clue The requirement says highest first.

Other CRM & Business Applications certifications

Study guides for exams that overlap with Mule-Dev-201.

Practise what you read

Mule-Dev-201 domains: common questions

How many domains are in the Mule-Dev-201 exam?

Mule-Dev-201 has 12 domains with 40 official objectives between them: Creating Application Networks, Designing APIs, Accessing and Modifying Mule Events, Structuring Mule Applications, Building API Implementation Interfaces, Using Connectors, Processing Records, Transforming Data, Routing Events, Handling Errors, Debugging and Troubleshooting Mule Applications and Deploying and Managing APIs and Integrations.

Which Mule-Dev-201 domain carries the most weight?

Accessing and Modifying Mule Events is the heaviest at 10%, followed by Structuring Mule Applications (10%). The lightest is Debugging and Troubleshooting Mule Applications (5%). Weights come from Salesforce's official outline.

What is the Mule-Dev-201 exam format?

Questions: 60 multiple-choice questions (plus up to 5 unscored questions). Time allowed: 120 minutes. Passing score: 70%.

How long should I study for Mule-Dev-201?

Our planning estimate is 66–89 hrs across all domains, split by weight. It is an editorial estimate, not an official figure, so adjust it to your experience and to how you score on practice questions.

Where should I start?

Start with Accessing and Modifying Mule Events, because it carries the most marks, then work down by weight. Use the checklist on each domain page to confirm you can do what the domain asks before moving on.

Which outline is this guide based on?

This guide follows Salesforce Certified MuleSoft Developer Exam Guide (Salesforce Help article 005298959; questions aligned to the Spring '24 release; 12 sections, 40 objectives) (current), published by Salesforce. It was last reviewed in October 2026.

Domain names, weights and objectives come from Salesforce's official outline (Salesforce Certified MuleSoft Developer Exam Guide (Salesforce Help article 005298959; questions aligned to the Spring '24 release; 12 sections, 40 objectives) (current)). Question counts and study hours are editorial planning estimates, not official figures. Last reviewed October 2026.