MCD-Level-1 MuleSoft Certified Developer - Level 1 (Mule 4) Free Practice Exam Questions (2025 Updated)

Debugger can be used to debug applications to see event data movine from one flow to other

In case of an error , batch job completes in flight steps and stops further processing.

MuleSoft Doc Ref : Handling Errors During Batch Job | MuleSoft Documentation

The default is all processing will stop but we can change it by Max Failed Record field.

General -> Max Failed Records: Mule has three options for handling a record-level error: Finish processing, Continue processing and Continue processing until the batch job accumulates a maximum number of failed records. This behavior can be controlled by Max Failed Records.

The default value is Zero which corresponds to Finish processing.

The value -1, corresponds to Continue processing.

The value +ve integer, corresponds to Continue processing until the batch job accumulates a maximum number of failed records

Metadata is stored in application-types.xml flle located under src/main/resources.

Mule 4 applications contain an application-types.xml file, which is where metadata around your data types is stored. For example, if you create a new CSV type, that metadata will be added to this file. This new file is easy to share, commit, and merge when conflicts arise, which enables you to do more metadata-driven development.

MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.3/intro-studio#metadata-storage

lookup(String, Any, Number)

This function enables you to execute a flow within a Mule app and retrieve the resulting payload.

It works in Mule apps that are running on Mule Runtime version 4.1.4 and later.

Similar to the Flow Reference component (recommended), the lookup function enables you to execute another flow within your app and to retrieve the resulting payload. It takes the flow’s name and an input payload as parameters. For example, lookup("anotherFlow", payload) executes a flow named anotherFlow.

Correct answer is

lookup( "createCustomerObject", {first: "Aice, last: "Green"})

MuleSoft Documentation Reference : https://docs.mulesoft.com/mule-runtime/4.3/dw-mule-functions-lookup

You can choose Attach Project Sources to include metadata that Studio requires to reimport the deployable file as an open Mule project into your workspace. You must keep the Attach Project Sources option selected to be able to import the packaged JAR file back into a Studio workspace. But requirement here is to create smallest deployable archive that will successfully deploy to Cloudhub. Hence we can ignore this option.

We need to select Include project module and dependencies

As actual modules and external dependencies required to run the Mule application in a Mule runtime engine

Hence correct answer is

Select only below option 2) Include project module and dependencies

MuleSoft Doc Ref : https://docs.mulesoft.com/studio/7.5/import-export-packages#exporting-a-studio-project-to-a-deployable-mule-application

Option 1 is the correct syntax

The List operation returns an array of messages in which: Each message holds the file’s content in its payload. The file’s attributes section carries the file’s metadata (such as name, creation time, and size). The payload is empty if the element is a folder.

Points to remember:

* XML must have a root element.

* XML only allows one root element

* To avoid multiple root issues, you must create a root element for the XML output, whenever we transform output

* When mapping array elements (JSON or JAVA) to XML, wrap the map operations in {(..)}

-{ } are defining the object

( ) are transforming each element in the array as a key/value pair

* The transformation to XML would fail if the above mentioned considerations were not taken into account.

* Thus the transformation script declares a root element as trains and wraps the data in “{( )}“.

Whenever you see such type of question, always look out for root element followed by {( )} wrapping map.

I call this a "Wrap The Map" scenario. Hope it would help you remember !

* To use custom modules, you need to import the module or functions you want to use by adding the import directive to the head of your DataWeave script, for example:

1) Does not identify any functions to import from the String module:

import dw::core::Strings

2) To identify a specific function to import from the String module:

import camelize, capitalize from dw::core::Strings

3) To import all functions from the String module:

import * from dw::core::Strings

The way you import a module impacts the way you need to call its functions from a DataWeave script. If the directive does not list specific functions to import or use * from to import all functions from a function module, you need to specify the module when you call the function from your script.

* In given scenario, it's mentioned to import all of the WebStore.dwl

So correct answer is:

WSDL is used to define the contract in case of SOAP . RAML/OAS is used to REST services

Mule applications can be scaled vertically by changing worker size. Mule applications can be scaled horizontally by adding more workers.

Correct answer is as below. On complete phase only has access to batch job result statistics and payload is not available.

Total Records Processed: 3

Successful Records: 3

Failed Records: 0

On Complete

During this phase, you can optionally configure the runtime to create a report or summary of the records it processed for the particular batch job instance. This phase exists to give system administrators and developers some insight into which records failed to address any issues that might exist with the input data.

Sample output is as below

Mule Ref Doc : https://docs.mulesoft.com/mule-runtime/4.3/batch-processing-concept#on-complete

Correct answer is MAJOR

MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards compatible manner, and PATCH version when you make backwards compatible bug fixes.

For details refer to this documentation : https://semver.org/

Choice router finds the FIRST true condition, then distribute the event to the ONE matched route.

MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.1/choice-router-concept

The Choice router dynamically routes messages through a flow according to a set of DataWeave expressions that evaluate message content. Each expression is associated with a different routing option. The effect is to add conditional processing to a flow, similar to an if/then/else code block in most programming languages.

Only one of the routes in the Choice router executes, meaning that the first expression that evaluates to true triggers that route’s execution and the others are not checked. If none of the expressions are true, then the default route executes.

Diagram Description automatically generated

Choice Router

The Choice router dynamically routes messages through a flow according to a set of DataWeave expressions that evaluate message content. Each expression is associated with a different routing option. The effect is to add conditional processing to a flow, similar to an if/then/else code block in most programming languages.

Only one of the routes in the Choice router executes, meaning that the first expression that evaluates to true triggers that route’s execution and the others are not checked. If none of the expressions are true, then the default route executes.

Properties of

PropertyDescription

Expression (expression)

Expression in DataWeave language to evaluate input.If the expression evaluates to true, this routing option is used:

Mulesoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.3/choice-router-concept

With respect to above information ,

Option 1 is the correct syntax as others are incorrect because of below reasons

* Single = is not the correct syntax to validate the condition. It should be ==

* If keyword is not required in when condition.