Mulesoft MCD-Level-1 Exam Questions

What are the latest specification of RAML available?

A. 1.2

B. 1

C. 0.8

D. 2

B. 1

Explanation:
The current version of the RAML specification is 1.0
You can check RAML version in RAML definition by referring to first comment. See highlighted part in below image.

Refer to the exhibits. The main flow contains an HTTP Request in the middle of the flow. The HTTP Listeners and HTTP Request use default configurations.
A web client submits a request to the main flow's HTTP Listener that includes query parameters for the pedigree of the piano.
What values are accessible to the Logger component at the end of the main flow?

A. payload

B. payload
pedigree query params

C. payload
producer var

D. payload
pedigree query params producer var

C. payload
producer var

In this case as outbound call is made using HTTP: POST /child , all attributes will be replaced by this invocation. Hence query parameter will not be accessible at logger. Hence correct answer is option 2.

Refer to the exhibits.

A JSON payload is set in the Set Payload transformer.
What is logged by the Logger?

A.

"String"

B.

"Object"

C.

"Array"

D.

"JSON"

C.

"Array"

Refer to the exhibit

What can be added to the flow to persist data across different flow executions?

A.

Key/value pairs in the ObjectStore

B.

Properties of the Mule runtime flowobject

C.

properties of the Mule runtime app object

D.

session variables

A.

Key/value pairs in the ObjectStore

What DataWeaveexpression transforms the example XML input to the CSV output?

A.

Option A

B.

Option B

C.

Option C

D.

Option D

A.

Option A

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 exhibits.

The Mule application implements a REST API that accepts GET requests from web clients on the URLs: http://acme com/order/status and http:Vacme.com/customer/status. What path value can be set in the HTTP GE~ event source to accept web client requests from both of these URLs?

A. *[order,customer]/status

B. */status

C. ?[order,customer]/status

D. *status

B. */status

Where is metadata stored in a Mule project

A. Config.yaml file

B. POM.xml file

C. application-types.xml

D. Global Element

C. application-types.xml

Explanation:
Metadata is stored in application-types.xml flle located under src/main/resources.
Mule 4 applications contain an application-types.xml file, which is where metadata around your data types is stored. For example, if you create a new CSV type, that metadata will be added to this file. This new file is easy to share, commit, and merge when conflicts arise, which enables you to do more metadata-driven development.