Mulesoft MCD-Level-1 Exam Questions

Refer to the exhibit.

How should the WHERE clause be changed to set the city and state values from the configured input parameters?

A. Option A

B. Option B

C. Option C

D. Option D

A. Option A

Which of the following is invalid type of event processor which can be used as a router?

A. Choice

B. Round Robin

C. Pick First

D. First Successful

C. Pick First

Pick First is not valid type. Rest all are valid type of event processor.

From which application , Organization Administrators can approve/revoke/delete SLA tier access requests.

A. API Exchange

B. API Portal

C. API Gateway

D. API Manager

Organization Administrators can approve/revoke/delete SLA tier access requests via API Manager only.

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

A. Option A

B. Option B

C. Option C

D. Option D

C. Option C

Refer to the exhibit.

All three of the condition for the Choice router are true. What log messages are written?

A. Route 1

B. Route2

C. Route1, Route2

D. Route1, Route2, Default

A. Route 1

Refer to theexhibits.

The main flow contains an HTTP Request. The HTTP Listeners and HTTP Request use
default configurations.
What values are accessible in the child flow after a web client submits a request to
http://localhost:8081/order? col or = red?

A.

payload

B.

payload
quantity var

C.

payload
color query param

D.

payload
quantity var color query param

A.

payload

An API has been created in Design Center. What is the next step to make the API discoverable?

A. Publish the API to Anypoint Exchange

B. Publish the API from inside flow designer

C. Deploy the API to a Maven repository

D. Enable autodiscovery in API Manager

A. Publish the API to Anypoint Exchange

Explanation:
Correct answer is Publish the API to Anypoint Exchange
Anypoint Exchange makes this possible by making it discoverable in below ways
1) In private exchange for internal developers
2) In a public portal for external developers/clients
Here is diagram created by me to help you understand sequence:

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