Mulesoft MCD-Level-1 Exam Questions

Refer to the exhibit.

What is the correct syntax to add a customer ID as a URI parameter in an HTTP Listener's path attribute?

A. (customerlD)

B. {customerlD}

C. #[customerlD]

D. ${ customerID}

B. {customerlD}

How we can scale deployed Mule application vertically on cloudhub?

A. Changing worker size

B. Adding multiple workers

C. Mule applications can be scaled only horizontally

D. Option 1 and 2 both can be used

A. Changing worker size

Explanation: Mule applications can be scaled vertically by changing worker size. Mule applications can be scaled horizontally by adding more workers.

A Scatter-Gather processes three separate HTTP requests. Each request returns a Mule event with a JSON payload. What is the final output of the Scatter-Gather?

A. An Array of the three Mule event Objects

B. An Object containing all three Mule event Objects

C. An Array of the three JSON payload Objects

D. An Object containing all three JSON payload Objects

B. An Object containing all three Mule event Objects

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

Which keyword do you use to create a new function in DataWeave?

A. function

B. fun

C. func

D. map

B. fun

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

Which of the below is not a valid category for connector type?

A. Gold

B. Select

C. Premium

D. Community

A. Gold

Gold is not valid category for connector types.

A shopping API contains a method to look up store details by department.
To get the information for a particular store, web clients will submit requests with a query parameter named department and uri parameter named storeId.
What is valid RAML snippet that supports requests from a web client to get a data for a specific storeId and department name?

A. 1./department:
2. get:
3. uriParameter:
4. storeId:

B. 1.get:
2.uriParameter:
3.{storeId}:
4.queryParameter:
5.department:

C. 1.get:
2. queryParameter:
3. department:
4. uriParameter:
5. {storeId}:

D. 1./{storeId}:
2. get:
3. queryParameter:
4. department:

What is the trait name you would use for specifying client credentials in RAML?

A. headers

B. client-id

C. client-id-required

D. cannot be specified in RAML

C. client-id-required

Explanation:
client-id-required enforces clients to add client_id and client_secret.
Please refer to below steps.
Add a section called traits: at the root level to define query parameters:
•traits:
- client-id-required:
queryParameters:
client_id:
type: string
client_secret:
type: string
2) Reference the trait in each of the methods to specify that each of the methods require these query parameters. After each method in the RAML file, add is:
[client-id-required]. For example:
/users:
get:
is: [client-id-required]
description: Gets a list of JSONPlaceholder users.

What happens to the attributes of a Mule event in a flow after an outbound HTTP Request is made?

A. Attributes are replaced with new attributes from the HTTP Request response (which might be null)

B. New attributes may be added from the HTTP response headers, but no headers are ever removed

C. Attributes do not change

D. Previous attributes are passed unchanged

A. Attributes are replaced with new attributes from the HTTP Request response (which might be null)

Explanation:
Attributes are replaced with new attributes from the HTTP Request response.
Attributes include everything apart from Payload/body. For ex: Headers, query parameters, URI parameters.
So, when outbound HTTP request is made, new attributes need to pass the outbound HTTP request and old attributes are replaced.
I have created below diagram to make it easy for you to understand: