Mulesoft MCD-Level-1 Exam Questions

229 Questions


Updation Date : 1-Jan-2026



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!

Refer to the exhibits.

The Batch job processes an array of strings.
What information is logged by the logger component after the batch job scope completes processing of the input payload?


A. Total Records Processed: 3
Successful Records: 3
Failed Records: 0
payload: ["A","B","C"]


B. ["A","B","C"]


C. Total Records Processed: 3
Successful Records: 3
Failed Records: 0
payload: ["a", "b", "c"]


D. Total Records Processed: 3
Successful Records: 3
Failed Records: 0





D.
  Total Records Processed: 3
Successful Records: 3
Failed Records: 0

Explanation:
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

What HTTP method in a RESTful web service is typically used to completely replace an existing resource?


A. GET


B. PATCH


C. PUT


D. POST





C.
  PUT

PUT replaces the original version of the resource, whereas the PATCH method supplies a set of instructions to modify the resource.

Refer to the exhibits The Mule application does NOT define any global error handlers.

A web client sends a POST request to the Multi application with this input payload The File Write operation throws a FILECONNECTIVITY error. What response message is returned to the web client?


A. "ORDER NOT_CREATED"


B. "OTHER ERROR"


C. "File written"


D. "FILECONNECTIVITY"





A.
  "ORDER NOT_CREATED"

Which of the below is not the mandatory configurations for HTTP Listener?


A. Path


B. Allowed methods


C. HTTP port in Connector Configuration


D. HTTP host in Connector Configuration





B.
  Allowed methods

Allowed methods is an optional configuration. If nothing is specified then all HTTP methods are supported. Rest all are mandatory.

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

Refer to the exhibits.

What is the response when a client submits a request to http://localhost:8081?


A. After


B. null


C. Before


D. Validation error





D.
  Validation error

Here’s specifically what is happening here:
1) Payload is successfully set to “Before”
2) Is null validation is used which will pass the message only if payload is null. In this case as payload is not null, it creates an Error Object. Flow execution stops
#[error.description] = “Validation error”
3) Because no error handler is defined, the Mule default error handler handles the error
4) “Validation error” is the error message returned to the requestor in the body of the HTTP request with HTTP Status Code: 500
Reference diagram:

Refer to the exhibit

What can be added to the flow to persist data across different flow executions?


A.

Key/value pairs in the ObjectStore


B.

Properties of the Mule runtime flowobject


C.

properties of the Mule runtime app object


D.

session variables





A.
  

Key/value pairs in the ObjectStore



What should this endpoint return?
http://dev.acme.com/api/patients?name=John&surname=Bell


A. Patient with name as John


B. Patient with surname as bell


C. Patients with either name as John or surname as Bell


D. Patients with name as John and surname as Bell





D.
  Patients with name as John and surname as Bell

Explanation:
Query parameters are a defined set of parameters attached to the end of a url. They are extensions of the URL that are used to help define specific content or actions based on the data being passed. To append query params to the end of a URL, a ‘?’ Is added followed immediately by a query parameter.
To add multiple parameters, an ‘&’ is added in between each.
Hence coming back to question, endpoint would return Patients with name as John and (and is very important here) surname as Bell.


Page 1 out of 29 Pages