Mulesoft MCD-Level-1 Exam Questions

229 Questions


Updation Date : 26-Nov-2025



Mulesoft MCD-Level-1 exam questions feature realistic, exam-like questions that cover all key topics with detailed explanations. You’ll identify your strengths and weaknesses, allowing you to focus your study efforts effectively. By practicing with our MCD-Level-1 practice test, you’ll gain the knowledge, speed, and confidence needed to pass the Mulesoft exam on your first attempt.

Why leave your success to chance? Our Mulesoft MCD-Level-1 dumps are your ultimate guide to passing the exam on your first try!

A Mule application contains an ActiveMQ JMS dependency. The Mule application was
developed in Anypoint Studio and runs successfully in Anypoint Studio.
The Mule application must now be exported from Anypoint Studio and shared withanother
developer. What export options create the smallest JAR file that can be imported into the other
developer's Anypoint Studio and run successfully


A.

Option A


B.

Option B


C.

Option C


D.

Option D





B.
  

Option B



Refer to the exhibits.

A web client submits the request to the HTTP Listener. What response message would be returned to web client?


A. End


B. String is not blank


C. No response would be sent back to client and request will get errored out in Mule


D. Start





B.
  String is not blank

Explanation:
Correct answer is String is not blank.
------------------------------------------------------------------------------------------------------------------------- 

Here’s specifically what is happening here:
1) Payload is successfully set to “Start”
2) The Is Blank String validator creates an Error Object because the payload is string "Start". Execution stops
#[error.description] = “String is not blank”
3) Because no error handler is defined, the Mule default error handler handles the error.
Remember, at its heart, the Mule Default Error handler is an error handling scope with just an on error propagate
4) “String is not blank” is the error message returned to the requestor in the body of the HTTP requestHTTP Status Code: 500
Reference Diagram:

Refer to the exhibits.

The Set Payload transformer's value is set to {'year': '2020'}.
What message value should be added to the Logger component to output the message
'The year is 2020', withouthardcoding 2020?


A.

#[The year is $(pay load .year)]*


B.

The year is #[payload.year]'


C.

'#[The year is " + paytoad.year]'


D.

#["The year is "++ payload.year].





D.
  

#["The year is "++ payload.year].



Refer to the exhibits.

The Mule application configures and uses two HTTP Listener global configuration elements.
Mule application is run in Anypoint Studio.
If the mule application starts correctly, what URI and port numbers can receive web client requests? If the mule applications fails to start , what is the reason for the failure?


A. The mule application fails to start. There is URL path conflict because both HTTP Listeners are configured with same path


B. The mule application start successfully Web client requests can only be received at URI on port 2222 but not on port 3333


C. The mule application fails to start because of the port binding conflict as HTTP request also use same port i.e. 3333


D. The mule application start successfully Web client requests can be received at URI on port 2222 and on port 3333.





D.
  The mule application start successfully Web client requests can be received at URI on port 2222 and on port 3333.

In this case both the flows can start without any error and requests can be received on both ports. Flow names httpListener1 can call other flow using HTTP request without any issues.

How we can scale deployed Mule application vertically on cloudhub?


A. Changing worker size


B. Adding multiple workers


C. Mule applications can be scaled only horizontally


D. Option 1 and 2 both can be used





A.
  Changing worker size

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

Following Mulesoft's recommended API-led connectivity approach , an organization has created an application network. The organization now needs to create API's to transform , orchestrate and aggregate the data provided by the other API's in the application network. This API should be flexible enought ot handle the data from additional API's in future. According to Mulesoft's recommended API-led connectivity approach , what is the best layer for this new API?


A. Process layer


B. System layer


C. Experience layer


D. Data layer





A.
  Process layer

Correct answer is process layer as all the orchestration and transformation logic should be in process layer as per Mulesoft's recommended approach for API led connectivity.

Refer to the exhibit.

The Database Select operation returns five rows from a database. What is logged by the Logger component?


A. "Array"


B. "Object"


C. "LinkedHashMap"


D. "CaselnsensitrveHashMap"





C.
  "LinkedHashMap"

A Mule project contains a DataWeave module like WebStore.dwl that defines a function named loginUser. The module file is located in the project's src/main/resources/libs/etl folder.
What is correct DataWeave code to import all of the WebStore.dwl file's functions and then call the loginUser function for the login "Todd.Pal@mulesoft.com"?


A. 1. 1. import libs.etl
2. 2. ---
3. 3. WebStore.loginUser("Todd.Pal@mulesoft.com")


B. 1. 1. import * from libs::etl
2. 2. ---
3. 3. WebStore::loginUser("Todd.Pal@mulesoft.com")


C. 1. 1. import libs.etl.WebStore
2. 2. ---
3. 3. loginUser("Todd.Pal@mulesoft.com")


D. 1. 1. import * from libs::etl::WebStore
2. 2. ---
3. 3. loginUser("Todd.Pal@mulesoft.com")





D.
  1. 1. import * from libs::etl::WebStore
2. 2. ---
3. 3. loginUser("Todd.Pal@mulesoft.com")

Explanation:
* 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:
Reference: https://docs.mulesoft.com/mule-runtime/4.3/dw-functions


Page 1 out of 29 Pages