Mulesoft MCD-Level-1 Exam Questions

229 Questions


Updation Date : 1-Dec-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!

Refer to the exhibits.

In the requestFlow an HTTP Request operation is configured to send an HTTP request with
an XML payload. The request is sent to the HTTP Listener in the transform Flow.
That flow transforms the incoming payload into JSON format and returns the response to
the HTTP request. The response of the request is storedin a target variable named the
Result.
What is the payload at the Logger component after the HTTP Request?


A.

A non-empty Java object


B.

The original XML payload


C.

null


D.

The returned JSON response





B.
  

The original XML payload



Refer to the exhibit.


The main flow contains a Flow Reference for the child flow.
What values are accessible in the child flow after a webclient submits a request to
http://localhost:8Q81/order? color=red?


A.

payload


B.

payload
quantity var


C.

payload
color query param


D.

payload
quantity var color query param





D.
  

payload
quantity var color query param



Mule application contains ActiveMQ JMS dependency. Mule application was compiled and run successfully in Anypoint Studio. The mule application must now be exported from Anypoint Studio and shared with other developer. What export options should be selected to create the smallest JAR file that can be imported into other developer's Anypoint Studio and run successfully?


A. Select only Attach Project Sources only


B. Select both Attach Project Sources and Include project modules and dependencies option


C. Select the Include project modules and dependencies option only


D. De-select both Attach Project Sources and Include project modules and dependencies option





A.
  Select only Attach Project Sources only

Explanation:
Correct answer is Select only Attach Project Sources only.
You must keep the Attach Project Sources option selected to be able to import the packaged JAR file back into a Studio workspace.
Deselect the Include project modules and dependencies option.
This option skips bundling the actual modules and external dependencies required to run the Mule application in a Mule runtime engine, creating a lightweight JAR file package that does not include any dependencies specified in the Mule application’s pom.xml file.
The generated JAR file is not a functional deployable archive and cannot be deployed to a Mule runtime engine, but instead offers a way to archive only the source files that make up the Mule application. This is the same as using the -lightWeightPackage flag when packaging using the Mule Maven Plugin and is useful if you want to distribute your project to other Studio installations because it only keeps a reference to all its dependencies.
When you import a lightweight package into Studio, all your dependencies are automatically downloaded.

A Utlility.dwl is located in a Mule project at src/main/resources/modules. The Utility.dwl file defines a function named encryptString that encrypts a String What is the correct DataWeave to call the encryptString function in a Transform Message component?


A. 1. %dw 2.0
2. output application/json
3. import modules::Utility
4. ---
5. Utility::encryptString( "John Smith" )


B. 1. %dw 2.0
2. output application/json
3. import modules::Utility
4. ---
5. encryptString( "John Smith" )


C. 1. %dw 2.0
2. output application/json
3. import modules.Utility
4. ---
5. encryptString( "John Smith" )


D. 1. %dw 2.0
2. output application/json
3. import modules.Utility
4. ---
5. Utility.encryptString( "John Smith" )





B.
  1. %dw 2.0
2. output application/json
3. import modules::Utility
4. ---
5. encryptString( "John Smith" )

Explanation: Correct answer is
%dw 2.0
output application/json
import modules::Utility
---
Utility::encryptString( "John Smith" )
DataWeave 2.0 functions are packaged in modules. Before you begin, note that DataWeave 2.0 is for Mule 4 apps. For Mule 3 apps, refer to DataWeave Operators in the Mule 3.9 documentation. For other Mule versions, you can use the version selector for the Mule Runtime table of contents.
Functions in the Core (dw::Core) module are imported automatically into your DataWeave scripts. To use other 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:
import dw::core::Strings
import camelize, capitalize from dw::core::Strings
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. For example, this import directive does not identify any functions to import from the String module, so it calls the pluralize function like this: Strings::pluralize("box").
Transform
%dw 2.0
import dw::core::Strings
output application/json
---
{ 'plural': Strings::pluralize("box") }

A flow needs to combine and return data from two different data sources. It contains a
Database SELECT operation followed by an HTTP Request operation.
What is the method to capture both payloads so the payload from the second request does
not overwrite that fromthe first?


A.

Put the Database SELECT operation inside a Cache scope


B.

Put the Database SELECT operation inside a Message Enricher scope


C.

Nothing, previous payloads are combined into the next payload


D.

Save the payload from the Database SELECT operation to a variable





D.
  

Save the payload from the Database SELECT operation to a variable



Which one of them is NOT a flow in Mule?


A. sync flow


B. subflow


C. async sub flow


D. async flow





C.
  async sub flow

Explanation:
Correct answer is async sub flow. Rest are valid flows in Mule.
Sub flow is always synchronous.

What is the correct Syntax to add a customer ID as a URI parameter in the HTTP listener's path attribute?


A. #[customerID]


B. $[customerID]


C. {customerID}


D. (customerID)





C.
  {customerID}

URL parameters are always accessed using { } like => {customerID}

Explanation: Correct answer is {customerID}.


A. var toUpper(userName) -> upper(userName)


B. fun toUpper(userName) = upper(userName)


C. fun toUpper(userName) -> upper(userName)


D. var toUpper(userName) = upper(userName)





B.
  fun toUpper(userName) = upper(userName)

A function named toUpper needs to be defined that accepts a string named userName and returns the string in uppercase.
What is the correct DW code to define the toUpper function?


Page 1 out of 29 Pages