Mulesoft MCD-Level-1 Exam Questions

A web client sends a request to http;//localhost:8081?dept=sales. What is the correct DataWeave expression to access the value of dept?

A.

attributes.queryParams.dept

B.

attributes.dept

C.

message.queryParams.dept

D.

vars.dept

A.

attributes.queryParams.dept

What is the correct Syntax to add a customer ID as a URI parameter in the HTTP listener's path attribute?

A. #[customerID]

B. $[customerID]

C. {customerID}

D. (customerID)

C. {customerID}

URL parameters are always accessed using { } like => {customerID}

What payload is returned by a Database SELECT operation that does not match any rows
in the database?

A.

false

B.

null

C.

Exception

D.

Empty Array

D.

Empty Array

A Mule project contains a MySQL Database dependency. The project is exported from
Anypoint Studio so it can be deployed to CloudHub.
What export options create the smallest deployable archive that will successfully deploy to
CloudHub? What export option create their smallest deployable archive that will successfully deploy to
CloudHub?

A.

Option A

B.

Option B

C.

Option C

D.

Option D

B.

Option B

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.

A Utlility.dwl is located in a Mule project at src/main/resources/modules. The Utility.dwl file defines a function named encryptString that encrypts a String What is the correct DataWeave to call the encryptString function in a Transform Message component?

A. 1. %dw 2.0
2. output application/json
3. import modules::Utility
4. ---
5. Utility::encryptString( "John Smith" )

B. 1. %dw 2.0
2. output application/json
3. import modules::Utility
4. ---
5. encryptString( "John Smith" )

C. 1. %dw 2.0
2. output application/json
3. import modules.Utility
4. ---
5. encryptString( "John Smith" )

D. 1. %dw 2.0
2. output application/json
3. import modules.Utility
4. ---
5. Utility.encryptString( "John Smith" )

B. 1. %dw 2.0
2. output application/json
3. import modules::Utility
4. ---
5. encryptString( "John Smith" )

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

Refer to the exhibits.

A web client submits the request to the HTTP Listener. What response message would be returned to web client?

A. End

B. String is not blank

C. No response would be sent back to client and request will get errored out in Mule

D. Start

B. String is not blank

Explanation:
Correct answer is String is not blank.
-------------------------------------------------------------------------------------------------------------------------

Here’s specifically what is happening here:
1) Payload is successfully set to “Start”
2) The Is Blank String validator creates an Error Object because the payload is string "Start". Execution stops
#[error.description] = “String is not blank”
3) Because no error handler is defined, the Mule default error handler handles the error.
Remember, at its heart, the Mule Default Error handler is an error handling scope with just an on error propagate
4) “String is not blank” is the error message returned to the requestor in the body of the HTTP requestHTTP Status Code: 500
Reference Diagram:

Refer to the exhibits.

A web client sends a POST request to the HTTP Listener with the payload "Hello-". What
response is returned to the web client?
What response is returned to the web client?

A.

Hello- HTTP-] MS2-Three

B.

HTTP-JMS2-Three

C.

Helb-JMS1-HTTP-JMS2 -Three

D.

Hello-HTTP-Three

A.

Hello- HTTP-] MS2-Three