Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.

AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by Mulesoft
Exam Format
Registration
Validity
Skills this practice test covers
- Write RAML for resources, methods, query parameters and reusable data types.
- Predict the payload, attributes and variables after a Flow Reference or an external call.
- Convert JSON, XML and Java data with DataWeave scripts, functions and custom types.
- Choose between On Error Continue, On Error Propagate and a Try scope for a failing flow.
- Process records with the For Each scope, a Batch Job and automatic watermarking.
- Deploy to CloudHub and secure the API in API Manager with autodiscovery and policies.
Explore related topics
MCD - Level 1 exam content
12 domains · 56 topics · 200 of 326 questions sorted by domain
Explaining Application Network Basics15 questions
This domain covers the ideas behind MuleSoft's approach: the IT delivery gap, API-led connectivity, application networks and the Center for Enablement (C4E). It also checks HTTP basics and the parts of Anypoint Platform used across the API lifecycle.
Skills tested
- Explain how API-led connectivity and an application network help close the IT delivery gap.
- Describe what a Center for Enablement (C4E) does and who takes part in it.
- Use the terms API, API implementation, API interface, API consumer and API invocation correctly.
- Describe the parts of an HTTP request and an HTTP response.
Questions by topic
- API-led Connectivity9
- Application Networks3
- API-led Connectivity Layers3
Designing and Consuming APIs12 questions
This domain is about the API specification. Candidates describe the lifecycle of the modern API, write RAML, and read a RAML spec to form correct requests.
Skills tested
- Define resources, nested resources and methods in RAML.
- Decide when a value belongs in a query parameter and when in a URI parameter.
- Define reusable data types and format-independent examples in RAML.
- Read a RAML spec and send a request with the right query parameters and headers.
Official topics
- Modern API Lifecycle
- RAML API Definition
- Consuming RESTful APIs
Accessing and Modifying Mule Events14 questions
A Mule event carries a message, made of a payload and attributes, plus variables through a flow. This domain checks that candidates can read and change each part.
Skills tested
- Describe the structure of a Mule event: payload, attributes and variables.
- Set the payload and variables with transformers such as Set Payload and Set Variable.
- Write DataWeave expressions that read and modify event data.
- Store an operation's result in a variable with a target parameter instead of the payload.
Official topics
- Mule Event Data Structure
- Transforming Mule Events
- DataWeave Expressions for Events
Structuring Mule Applications19 questions
This domain is about organizing an application so that it is easy to change and reuse. Candidates parameterize settings, share global configurations and split logic into flows, then predict which data survives each kind of call.
Skills tested
- Parameterize an application with property placeholders.
- Define global elements once and reuse them across flows.
- Split logic into private flows and subflows called with a Flow Reference.
- Predict which payload, attributes and variables remain after a Flow Reference, a connection boundary or an external call.
Official topics
- Application Parameterization
- Global Configurations
- Flow Organization
Building API Implementation Interfaces10 questions
Here a RAML specification becomes a working interface. Candidates build a REST interface by hand, generate a REST Connector from RAML, and use APIkit to create flows and route requests.
Skills tested
- Create a RESTful interface for a Mule application by hand.
- Generate a REST Connector from a RAML specification.
- Use APIkit to create implementation flows from a RAML file.
- Explain how the APIkit Router sends each request to the matching flow.
Questions by topic
- APIkit Framework7
- SOAP Web Services2
- APIkit Request Validation1
Routing Events16 questions
This domain controls the path an event takes through a flow. Candidates route with the Choice router, send an event down several routes at once with Scatter-Gather, and check data with the Validation module.
Skills tested
- Route events with the Choice router, including its default route.
- Multicast an event with Scatter-Gather and read the combined result.
- Reject bad input with the Validation module.
Official topics
- Choice Router
- Scatter-Gather Router
- Data Validation
Handling Errors15 questions
Error handling decides what the caller receives when a step fails. Candidates work with the default handler, a custom global handler, flow-level handlers, the Try scope and error mappings.
Skills tested
- Compare On Error Continue and On Error Propagate and predict the response each one returns.
- Define a custom global default error handler and know when it is used.
- Wrap event processors in a Try scope with their own error handlers.
- Read the Mule Error object and map errors to custom application errors.
Official topics
- Default Error Handling
- Custom Global Error Handlers
- On Error Scopes
- Flow-Level Error Handlers
- Try Scope
- Error Object Structure
- Custom Application Errors
Transforming Data with DataWeave25 questions
DataWeave is MuleSoft's language for transforming data. This domain covers scripts that convert JSON, XML and Java structures, built-in functions, variables, modules, custom types and calls to Mule flows.
Skills tested
- Convert between JSON, XML and Java data structures in a DataWeave script.
- Use built-in DataWeave functions, such as those for arrays and dates.
- Define DataWeave variables, functions, modules and custom data types.
- Call a Mule flow from a DataWeave script.
Questions by topic
- Conditional Object Fields4
- DataWeave Functions3
- Calling Mule Flows from DataWeave6
- DataWeave Functions and Selectors5
- Data Serialization3
- Data Type Conversion2
- Date and Time Functions1
- DataWeave Grouping and Sorting1
Using Connectors19 questions
Connectors link a Mule application to outside systems. Candidates query databases, call REST and SOAP services, read and write local and remote files, and publish and listen for JMS messages.
Skills tested
- Retrieve data with the Database connector and parameterized SQL queries.
- Call a REST service with the HTTP Request operation or a REST Connector.
- Consume a SOAP web service with the Web Service Consumer, passing arguments through Transform Message.
- List, read and write files with the File and FTP connectors.
- Publish and listen for messages with the JMS connector.
Official topics
- Database Connector
- HTTP Request and REST Connector
- Web Service Consumer
- File Connector
- FTP Connector
- JMS Connector
Processing Records23 questions
This domain compares the ways to handle each record in a collection. Candidates choose between the For Each scope and a Batch Job, trigger flows on a schedule or from a listener, and pick up only new records with watermarking.
Skills tested
- Process a collection with the For Each scope and predict the payload afterwards.
- Build a Batch Job with Batch Steps and a Batch Aggregator.
- Trigger a flow with the Scheduler component or a connector listener.
- Compare automatic and manual watermarking.
Questions by topic
- Batch Processing vs For Each2
- Scheduler Component4
- Watermarking4
- Batch Job3
- Batch Job Variable Scope2
- For Each Scope Variable Behavior2
- Batch Job vs For Each5
- Streaming and Event Processing Order1
Debugging and Troubleshooting Mule Applications14 questions
This domain is about finding faults in Anypoint Studio. Candidates inspect a Mule event at a breakpoint, install missing Maven dependencies and read Mule log error messages.
Skills tested
- Set breakpoints and inspect a Mule event in the Anypoint Studio debugger.
- Install missing Maven dependencies.
- Read a Mule log error message and find the component that failed.
Official topics
- Using Breakpoints
- Maven Dependencies
- Reading Log Errors
Deploying and Managing APIs and Integrations18 questions
The last domain takes an application live. Candidates package and deploy it to CloudHub, create API proxies, connect the implementation to API Manager, and protect the API with policies and SLA tiers.
Skills tested
- Package a Mule application and deploy it to CloudHub with the right properties.
- Create and deploy an API proxy.
- Connect an API implementation to API Manager with autodiscovery.
- Apply client ID enforcement and SLA-based policies with SLA tiers.
Questions by topic
- CloudHub Worker Behavior3
- API Policies6
- API Autodiscovery4
- Application Packaging3
- Secure Properties in CloudHub1
- SLA Tiers and Policies1
Requirements
- No formal prerequisites: MuleSoft sets no required exam or course.
- Recommended: some object-oriented programming, preferably in Java.
- Recommended: working knowledge of HTTP, REST, SOAP, JMS and JDBC, and of the XML, CSV and JSON formats.
- Recommended: hands-on time in Anypoint Studio, such as the exercises in MuleSoft's Fundamentals course.
About the MCD - Level 1 exam
MCD - Level 1 checks that a junior developer can design, build, test, debug, deploy and manage basic APIs and integrations with Mule 4. The work moves between Anypoint Platform, where the API is specified in RAML and managed, and Anypoint Studio, where the Mule application is built and debugged. Questions also cover DataWeave, connectors, routers, error handling and batch processing. Passing earns the MuleSoft Certified Developer - Level 1 credential, which Salesforce now issues as Salesforce Certified MuleSoft Developer.
DataWeave and record processing get the most questions in the PlanetCert practice test, followed by application structure and connectors. The explanations trace what the payload, attributes and variables hold at each step, for example after a Flow Reference or a call across a connection boundary. Study Mode suits the error handling questions, where On Error Continue and On Error Propagate send the caller different responses. Brainy AI Assistant can walk through a DataWeave script line by line, or write a new question on the same Batch Job case.
How to earn the certification
- Earns
- MuleSoft Certified Developer - Level 1 (Mule 4)Associate (Developer Level 1)
The certification is valid for two years from the date of passing.
How to prepare for MCD - Level 1
- 1
Match the booking page to this guide
MuleSoft certifications are now booked through Salesforce, where this exam appears as Salesforce Certified MuleSoft Developer. Check that its exam guide lists the same objectives before planning study time.
- 2
Build one API from spec to CloudHub
Write a small RAML spec in Anypoint Platform, generate flows from it with APIkit in Anypoint Studio, connect a database, and deploy the result to CloudHub. Most domains reuse this one project.
- 3
Watch the event change in the debugger
Many questions ask what the payload, attributes and variables hold after a Flow Reference, an HTTP call or a target parameter. Set breakpoints and watch each part change.
- 4
Write DataWeave every day
DataWeave has the most questions in the practice test. Convert JSON to XML and back, use date and array functions, and call a flow from a script until the syntax comes without notes.
- 5
Time a full run, then fix the misses
Take the MCD - Level 1 practice test in Timed Mode, then redo the missed error handling and Batch Job questions in Study Mode. Ask Brainy AI Assistant about any output that came as a surprise.
Start a timed MCD - Level 1run
MuleSoft recommends its Anypoint Platform Development: Fundamentals (Mule 4) course, in a class or as self-study, with the course's practice exercises and self-assessment quiz.
Who MCD - Level 1 is for
- Developers new to Mule 4 who build APIs and integrations while a senior developer reviews the work.
- Java developers moving into integration work on Anypoint Platform.
- Consultants on MuleSoft projects who need a first developer credential.
Typical job titles: MuleSoft developer · Integration developer · API developer · Junior integration engineer
MCD - Level 1 glossary
20 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- Anypoint Platform
- MuleSoft's platform for designing, building, deploying and managing APIs and integrations.
- Anypoint Studio
- MuleSoft's desktop development environment for building, testing and debugging Mule applications.
- API-led connectivity
- An approach that connects systems through reusable APIs in three layers: System APIs, Process APIs and Experience APIs.
- APIkit Router
- The APIkit component that checks each request against the RAML file and sends it to the matching implementation flow.
- Autodiscovery
- The setting that links a deployed API implementation to its API in API Manager, so that the API's policies apply to it.
- Automatic watermarking
- A connector feature that remembers the last record it processed, so that each poll picks up only new records.
- Batch Job
- A scope that splits a large set of records and runs each record through a series of Batch Steps.
- Center for Enablement (C4E)
- A cross-team group that builds and shares reusable assets and good practice, so that other teams can deliver integrations themselves.
- Client ID enforcement
- A policy that lets only registered client applications with a valid client ID and secret call the API.
- CloudHub
- MuleSoft's cloud service for running Mule applications.
- DataWeave
- MuleSoft's expression and transformation language for reading and changing data inside a Mule application.
- Flow Reference
- A component that calls another flow or subflow by name from inside a flow.
- IT delivery gap
- The growing difference between what the business asks IT to deliver and what IT can deliver with its resources.
- Mule event
- The object that moves through a flow. It holds a message, made of a payload and attributes, plus variables.
- On Error Continue
- An error handler scope that handles the error and ends the flow as a success, so that the caller gets a normal response.
- On Error Propagate
- An error handler scope that handles the error and then raises it again, so that the caller receives an error.
- Property placeholders
- Names in a configuration that are filled from a properties file at run time, so that settings can change by environment.
- RAML
- RESTful API Modeling Language: a text format for describing an API's resources, methods, parameters, data types and responses.
- Scatter-Gather
- A router that sends a copy of the event down several routes at the same time and combines their results.
- Try scope
- A scope that wraps one or more event processors and gives them their own error handlers.