Free MCD-Level-1 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

Correct answer is /accounts?account_type=retail&industry=finance

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.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/MuleSoft_MCD-Level-1/page_61_img_2.jpg

:

Scatter-Gather sends the event to each routes concurrently. Hence both route in this example will

start in parallel. So total time to complete processing is 40 seconds

The Scatter-Gather component is a routing event processor that processes a Mule event through

different parallel processing routes that contain different event processors. Each route receives a

reference to the Mule event and executes a sequence of one or more event processors. Each of these

routes uses a separate thread to execute the event processors, and the resulting Mule event can be

either the same Mule event without modifications or a new Mule event with its own payload,

attributes, and variables. The Scatter-Gather component then combines the Mule events returned by

each processing route into a new Mule event that is passed to the next event processor only after

every route completes successfully.

The Scatter-Gather component executes each route in parallel, not sequentially. Parallel execution of

routes can greatly increase the efficiency of your Mule application and may provide more

information than sequential processing.

Mule Ref Doc : https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept

:

:

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") }

In this case as outbound call is made using HTTP: POST /child , all attributes will be replaced by this

invocation. Hence query parameter will not be accessible at logger. Hence correct answer is option 2

:

The HTTP 415 Unsupported Media Type client error response code indicates that the server refuses

to accept the request because the payload format is in an unsupported format. The format problem

might be due to the request's indicated Content-Type or Content-Encoding , or as a result of

inspecting the data directly. As per RAML input is expected in application/xml.

Hence correct answer is Set a request header with the name Content-Type to a

:

URI parameter is basically used to identify a specific resource or resources

* Here we want to update details about specific department, so question is asking 'How to use URI

parameter' in RAML

* Correct answer is

/departments:

/{deptId}:

patch:

Reference: https://docs.mulesoft.com/design-center/design-common-problems-raml-10

:

:

MuleSoft Documentation Reference : https://docs.mulesoft.com/db-connector/1.9/databaseconnector-select

Note that private flow has error scope defined as On Error Continue . So when error occurs in private

flow , it is handled by this On Error Continue scope which sends success response back to main flow

and does not throw back an error. So main continues normally and payload is set to Success - main

flow.

Hence correct answer is Success - main flow

1) HTTP listener received request

2) The Flow Reference calls the child flow

3) The Is Number validator creates an Error Object because the payload isn’t an integer. Child Flow

execution stops

#[error.description] = “payload is not a valid INTEGER value”

#[error.errorType] = VALIDATION:INVALID_NUMBER

4) The On Error Continue handles the errorThe payload is set to “Error – Sub Flow”

5) “Error – Sub Flow” is returned to the main flow as if the child flow was a success. The Set Payload

is executed. The payload is reset to “Success – Finished Main Flow”

6) “Success – Main Flow” is returned to the requestor in the body of the HTTP request. HTTP Status

Code: 200

As you can see, in the above example, because the error was caught by an On Error Continue scope

in the child flow (RED in, GREEN out) when the Mule Message returns to the parent flow, the parent

flow knows none-the-different that there was a failure because the on error continue returns a 200

success message. Note that because, to the mainFlow, the childFlow appeared to succeed, the

processing of mainFlow resumed after the flow reference.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/MuleSoft_MCD-Level-1/page_42_img_1.jpg

:

For Each Scope

The For Each scope splits a payload into elements and processes them one by one through the

components that you place in the scope. It is similar to a for-each/for loop code block in most

programming languages and can process any collection, including lists and arrays. The collection can

be any supported content type, such as application/json, application/java, or application/xml.

General considerations about the For Each scope:

By default, For Each tries to split the payload. If the payload is a simple Java collection, the For Each

scope can split it without any configuration. The payload inside the For Each scope is each of the split

elements. Attributes within the original message are ignored because they are related to the entire

message.

For Each does not modify the current payload. The output payload is the same as the input.

Mule Doc Reference : https://docs.mulesoft.com/mule-runtime/4.3/for-each-scope-concept

:

:

Correct answer is as below.

After all processing routes have finished execution, the Scatter-Gather component creates a new

Mule event that combines all resulting Mule events from each route, and then passes the new Mule

event to the next component in the flow.

{

"0": {

"attributes": ...,

"payload": "100"

},

"1": {

"attributes": ...,

"payload": "200"

}

}

Bottom of Form