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 payload.

The Set payload transformer sets the payload to an object. The logger component's message attribute is configured with the string "Result #["INFO"++ payload]" What is the output of logger when this flow executes?


A. Result INFOpayload


B. Result INFO{"student":{"name":"Anay","age":6}}


C. 1. 1. "You called the function '++' with these arguments:
2. 2. 1: String ("INFO")
3. 3: Object ({student: {name: "Anay" as String {class: "java.lang.String"},age: 6 as Numbe...)


D. Error : You evaluated inline expression # without ++





C.
  1. 1. "You called the function '++' with these arguments:
2. 2. 1: String ("INFO")
3. 3: Object ({student: {name: "Anay" as String {class: "java.lang.String"},age: 6 as Numbe...)

Explanation:
Correct answer is as below as concatenation operation works only with string and not with the objects. In this case payload is object.
"You called the function '++' with these arguments:
1: String ("INFO")
2: Object ({student: {name: "Anay" as String {class: "java.lang.String"},age

Refer to theexhibits.

A Mule application has an HTTP Request that is configured with hardcoded values. To
change this, the Mule application is configured to use a properties file named config.yaml.
what valid expression can the HTTP Request host value be set to so that it is no longer
hardcoded?


A.

${training.host}


B.

${training:host}


C.

#[training:host]


D.

#[training.host]





A.
  

${training.host}



An API instance of type API endpoint with API proxy is created in API manager using an API specification from Anypoint Exchange. The API instance is also configured with an API proxy that is deployed and running in CloudHub.
An SLA- based policy is enabled in API manager for this API instance.
Where can an external API consumer obtain a valid client ID and client secret to successfully send requests to the API proxy?


A. In the organization's public API portal in Anypoint Exchange, from an approved client application for the API proxy


B. In Anypoint Studio, from components generated by APIkit for the API specification


C. In Anypoint Studio, from components generated by Rest Connect for API specification


D. In Runtime Manager, from the properties tab of the deployed approved API proxy





A.
  In the organization's public API portal in Anypoint Exchange, from an approved client application for the API proxy

Explanation:
* When a client application is registered in Anypoint Platform, a pair of credentials consisting of a client ID and client secret is generated.
* When the client application requests access to an API, a contract is created between the application and that API.
* An API that is protected with a Client ID Enforcement policy is accessible only to applications that have an approved contract.
-------------------------------------------------------------------------------------------------------------------------
Correct Answer: In the organization's public API portal in Anypoint Exchange, from an approved client application for the API proxy.

What is the difference between a subflow and a sync flow?


A. No difference


B. Subflow has no error handling of its own and sync flow does


C. Sync flow has no error handling of its own and subflow does


D. Subflow is synchronous and sync flow is asynchronous





B.
  Subflow has no error handling of its own and sync flow does

Explanation:
Correct answer is Subflow has no error handling implementation where as sync flow has Subflow:
A subflow processes messages synchronously (relative to the flow that triggered its execution) and always inherits both the processing strategy and exception strategy employed by the triggering flow. While a subflow is running, processing on the triggering flow pauses, then resumes only after the subflow completes its processing and hands the message back to the triggering flow.
Synchronous Flow:
A synchronous flow, like a subflow, processes messages synchronously (relative to the flow that triggered its execution). While a synchronous flow is running, processing on the triggering flow pauses, then resumes only after the synchronous flow completes its processing and hands the message back to the triggering flow. However, unlike a subflow, this type of flow does not inherit processing or exception strategies from the triggering flow.
This type of flow processes messages along a single thread, which is ideally suited to transactional processing.

Refer to the exhibit.


The input array of strings is passed to the batch job, which does NOT do any filtering or aggregating. What payload is logged by the Logger component?


A. Summary report of processed records


B. [ "Apple", "Banana" ]


C. [ "Apple12", "Banana12" ]


D. [ "Apple1", "Banana1", 2 ]





A.
  Summary report of processed records

Refer to the exhibits.

The main flow contains a Flow Reference component configured to call the child flow What part(s) of a Mule event passed to the Flow Reference component are available in the child flow?


A. The payload and all attributes


B. The payload and all variables


C. The entire Mule event


D. The payload





B.
  The payload and all variables

Refer to the exhibits.

The<when> expression for the Choice router needs to be written.
What is a valid <when> expression to route Mule events to the non-default flow?


A.

#['MuleSoft' == paytoad.company]


B.

#[ company = "MuleSoft" ]


C.

#[ if( company = "MuleSoft") ]


D.

#[ if('MuleSoff == payload.company) ]





A.
  

#['MuleSoft' == paytoad.company]



Where is metadata stored in a Mule project


A. Config.yaml file


B. POM.xml file


C. application-types.xml


D. Global Element





C.
  application-types.xml

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


Page 1 out of 29 Pages