MCD-Level-1 Exam Dumps - MuleSoft Certified Developer Questions and Answers

Empty array is returned when no rows are matched.

MuleSoft Doc Ref : https://docs.mulesoft.com/db-connector/1.9/database-connector-select

This is a trick question.

You can call only flows from DataWeave using lookup function. Note that lookup function does not support calling subflows.

A subflow needs a parent context to inherit behaviors from such as exception handling, which a flow does not need

Hence correct answer is Not possible in Mule 4

Correct answer is vars."customer"."firstName"

Please note that you can also access firstName using this syntax vars.customer.firstName.

Mule Ref Doc : Variables in Mule Apps | MuleSoft Documentation

As dependency is not present in Mulesoft Maven repository, we need to install the dependency on computer's local Maven repository.

https://docs.mulesoft.com/mule-runtime/4.3/maven-reference

You can define your own DataWeave functions using the fun declaration in the header of a DataWeave script. Sample is as below. ----------------------------------------

%dw 2.0

output application/json

fun toUpper(aString) = upper(aString)

---

toUpper("hello")

MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.1/dataweave-functions

Correct answer is An Object containing all three Mule event Objects

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.

Sample output is as below

Table Description automatically generated with low confidence

MuleSoft Documentation reference : https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept

API portal are created by API Exchange and cannot be created by Design Center

Option 2 is the correct answer as /api/* accespts everything starting with /api/