Mulesoft MCD-Level-2 Exam Questions

47 Questions


Updation Date : 15-Dec-2025



Mulesoft MCD-Level-2 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-2 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-2 dumps are your ultimate guide to passing the exam on your first try!

In a Mule project, Flow-1 contains a flow-ref to Flow-2 depends on data from Flow-1 to execute successfully. Which action ensures the test suites and test cases written for Flow-1 and Flow-2 will execute successfully?


A.

Chain together the test suites and test cases for Flow-1 and Flow-2


B.

Use ‘’Set Event to pass the input that is needed, and keep the test cases for Flow-1 and Flow-2 Independent


C.

Use ‘’Before Test Case’’ To collect data from Flow-1 test cases before running Flow-2 test cases


D.

Use ‘After Test Case’ to produce the data needed from Flow-1 test cases to pass to Flow-2 test cases





B.
  

Use ‘’Set Event to pass the input that is needed, and keep the test cases for Flow-1 and Flow-2 Independent



Explanation
To ensure the test suites and test cases written for Flow-1 and Flow-2 will execute successfully, the developer should use a Set Event processor to pass the input that is needed by Flow-2, and keep the test cases for Flow-1 and Flow-2 independent. This way, the developer can isolate the testing of each flow and avoid coupling them together.


References:
https://docs.mulesoft.com/munit/2.3/munit-test-flow

Multiple individual Mute application need to use the Mule Maven plugin to deploy to CloudHub.
The plugin configuration should .. reused where necessary and anything project, specific should be property-based.
Where should the Mule Maven details be configured?


A.

A parent pom.xml


B.

Settings, xml


C.

Pom, xml


D.

A Bill of Materials (BOM) parent pm





A.
  

A parent pom.xml



Explanation:
To reuse Mule Maven plugin configuration across multiple individual Mule applications, the developer should use a parent pom.xml file. A parent pom.xml file defines common configuration for one or more child projects that inherit from it. The developer can specify common properties and dependencies for all child projects in the parent pom.xml file, such as Mule Maven plugin configuration, and then reference them in each child project’s pom.xml file using placeholders. 

References:
https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#parent-pom
https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance

A Mule application deployed to multiple Cloudhub 2.0 replicas needs to temporarily persist large files over 10MB between flow executions, and routinely needs to query whether the file data exists on separate executions. How can this be achieved?

 


A.

Store the contents of the file on separate storage, and store the key and location of the file Object using Object Store v2


B.

Use an in-memory Object Store


C.

Store the key and full contents of the file in an Object Store


D.

Store the key and full contents of the file, caching the filename and location between requests





A.
  

Store the contents of the file on separate storage, and store the key and location of the file Object using Object Store v2



To temporarily persist large files over 10MB between flow executions, and routinely query whether the file data exists on separate executions, the developer should store the contents of the file on separate storage, and store the key and location of the file object using Object Store v2. This way, the developer can avoid storing large files in memory or exceeding the size limit of Object Store v2 (10MB per object). The developer can also use Object Store v2 operations to query, retrieve, or delete the file object by its key.

References:
https://docs.mulesoft.com/object-store/osv2-faq#can-i-store-files-in-object-store-v2

 

An order processing system is composed of multiple Mule application responsible for warehouse, sales and shipping. Each application communication usingAnypoint MQ. Each message must be correlated against the original order ID for observability and tracing. How should a developer propagate the order ID as the correlation ID across each message?


A. Use the underlying HTTP request of Anypoint MQ to set the‘X-CORRELATION_ID’ header to the orderID


B. Set a custom Anypoint MQ user propertyto propagate the order ID and set the correlation ID in the receiving applications.


C. Use the default correlation ID, Anypoint MQ will sutomatically propagate it.


D. Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID





D.
  Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID

A scatter-gather router is configured with four routes:Route A, B, C and D.

Route C false.


A.

Error,errorMesage.payload.results [‘2’]


B.

Payload failures[‘2’]


C.

Error,errorMessage,payload.failures[‘2’]


D.

Payload [‘2’]





C.
  

Error,errorMessage,payload.failures[‘2’]



Explanation:
The result of accessing route C failure is Error,errorMessage,payload.failures[‘2’]. This is because a scatter-gather router returns an aggregated message that contains an array of results from each route and an array of failures from each route. The failures array contains error objects with information about each failed route execution. To access route C failure, which is the third route (index 2), the developer needs to use Error.errorMessage.payload.failures[‘2’] expression. 

References:
https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-reference#scatter-gather-output

Which pattern can a web API use to notify its client of state changes as soon as they occur?


A.

HTTP Webhock


B.

Shared database trigger


C.

Schedule Event Publisher


D.

ETL data load





A.
  

HTTP Webhock



Explanation:
A web API can use HTTP Webhook to notify its client of state changes as soon as they occur. A webhook is an HTTP callback that allows an API to send real-time notifications to another system or application when an event happens. The client registers a URL with the API where it wants to receive notifications, and then the API sends an HTTP request to that URL with information about the event. 

References:
https://docs.mulesoft.com/connectors/webhook/webhook-connector

A company deploys 10 public APIs to CloudHub. Each API has its individual health endpoint defined. The platform operation team wants to configure API Functional Monitoring to monitor the health of the APIs periodically while minimizing operational overhead and cost.
How should API Functional Monitoring be configured?


A.

From one public location with each API in its own schedule


B.

From one private location with all 10 APIs in a single schedule


C.

From one public location with all 10 APIs in a single schedule


D.

From 10 public locations with each API in its own schedule





C.
  

From one public location with all 10 APIs in a single schedule



Explanation:
To configure API Functional Monitoring to monitor the health of 10 public APIs periodically while minimizing operational overhead and cost, the developer should use one public location with all 10 APIs in a single schedule. A public location is a worker that runs in a CloudHub shared environment, which is cheaper and easier to maintain than a private location. A single schedule allows running all 10 APIs tests at the same time and frequency, which reduces complexity and resource consumption. 

References:
https://docs.mulesoft.com/functional-monitoring/fm-create-monitor#create-a-monitor

A Mule application includes a subflow containing a Scatter.Gather scope. Within each log of the Scatter.Gatter. an HTTP connector calls a PUT endpoint to modify records in different upstream system. The subflow is called inside an Unit successful scope to retry if a transitory exception is raised. A technical spike is being performed to increase reliability of the Mule application. Which steps should be performed within the Mule flow above the ensure idempontent behavior?


A.

Change the PUT requests inside the Scatter-Gather to POST requests


B.

Ensure an error-handling flow performs corrective actions to roll back all changes if any leg of the Scatter-Gather fails


C.

Remove the Put requests from the Scatter-Getter and perform them sequentially


D.

None, the flow already exhibits idempotent behavior





B.
  

Ensure an error-handling flow performs corrective actions to roll back all changes if any leg of the Scatter-Gather fails



To ensure idempotent behavior within a Mule flow that contains a subflow with a Scatter-Gather scope, the developer should ensure an error-handling flow performs corrective actions to roll back all changes if any leg of the Scatter-Gather fails. Idempotency means that multiple identical requests have the same effect as a single request. Therefore, if one of the HTTP requests inside the Scatter-Gather fails, the error-handling flow should undo any changes made by other successful requests to ensure consistency and avoid partial updates.

References:
https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept
https://docs.mulesoft.com/mule-runtime/4.3/error-handling


Page 1 out of 6 Pages