Mulesoft MCD-Level-1 Exam Questions

Refer to the exhibits.

What is written to the records.csv file when the flow executes?

A. The JSON payload

B. An error message

C. Nothing

D. The payload convert to CVS

A. The JSON payload

Explanation: Transform Message Add write_date is coverting payload in JSON format and same JSON payload is avaialble to file write processor. However, if the payload is a different format (for example, not CSV) , you can place the transformation inside the Write operation to generate content that will be written without producing a side effect on the message in transit. This is not done in this case. By default, the connector writes whatever is in the message payload. Hence JSON payload will be written to file.

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

Refer to the exhibits.

The<when> expression for the Choice router needs to be written.
What is a valid <when> expression to route Mule events to the non-default flow?

A.

#['MuleSoft' == paytoad.company]

B.

#[ company = "MuleSoft" ]

C.

#[ if( company = "MuleSoft") ]

D.

#[ if('MuleSoff == payload.company) ]

A.

#['MuleSoft' == paytoad.company]

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 MuleSoft API-led connectivity layer is intended to expose part of a backend database without business logic?

A. Data layer

B. Process layer

C. Experience layer

D. System layer

Explanation:
Correct answer is System layer
System APIs provide a means for insulating the data consumers from the complexity or changes to the underlying backend systems.
MuleSoft recommends three-layered approach to API-led connectivity, highlighting the three layers:
* System APIs
* Process APIs
* Experience APIs
System APIs are the core systems of record underlying core systems of record (e.g. ERPs, key customer and billing systems, databases, etc.). Process APIs allow you to define a common process which the organization can share, and these APIs perform specific functions, provide access to non-central data, and may be built by either Central IT or Line of Business IT. And finally, the Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source.
The three-layered structure allows for a seamless flow of data from systems of record to new experiences, and allows for reusability of assets rather than point to point connections.
This approach provides a distributed and tailored approach to architecture, greater flexibility through loose coupling, and deeper operational visibility into what is being built.

Refer to the exhibit.

The Database Select operation returns five rows from a database. What is logged by the Logger component?

A. "Array"

B. "Object"

C. "LinkedHashMap"

D. "CaselnsensitrveHashMap"

C. "LinkedHashMap"

Refer to the exhibits.

Client sends the request to ClientRequestFlow which calls ShippingFlow using HTTP Request activity.
During E2E testing it is found that that HTTP:METHOD_NOT_ALLOWED error is thrown whenever client sends request to this flow.
What attribute you would change in ClientRequestFlow to make this implementation work successfully?

A. Change the method attribute value to "*’’

B. Change the path attribute value to "/api/ship"

C. Change the allowed method attributes value to "POST"

D. Change the protocol attribute value to "HTTPS"

C. Change the allowed method attributes value to "POST"

Explanation:
Correct answer is Change the method attributes value to "POST".
It can be fixed in either of the two ways as below.
1) Changing method attribute to POST in ClientRequestFlow
2) Setting allowedMethods as PUT in ShippingFlow (but doesn't fit as question mentions about changing ClientRequestFlow)

Refer to the exhibits.

The Mule application configures and uses two HTTP Listener global configuration elements.
Mule application is run in Anypoint Studio.
If the mule application starts correctly, what URI and port numbers can receive web client requests? If the mule applications fails to start , what is the reason for the failure?

A. The mule application fails to start. There is URL path conflict because both HTTP Listeners are configured with same path

B. The mule application start successfully Web client requests can only be received at URI on port 2222 but not on port 3333

C. The mule application fails to start because of the port binding conflict as HTTP request also use same port i.e. 3333

D. The mule application start successfully Web client requests can be received at URI on port 2222 and on port 3333.

In this case both the flows can start without any error and requests can be received on both ports. Flow names httpListener1 can call other flow using HTTP request without any issues.