Mulesoft MCD-Level-1 Exam Questions

Refer to the exhibits.

What DataWeave expression transforms the conductorIds array to the XML output?

A. 1. 1. trains:
2. 2. conductorIds map ((engId, index) ->
3. 3. train: {
4. 4. engineerId: engId
5. 5. }
6. 6. )

B. 1. 1. { trains:
2. 2.
3. 3. conductorIds map ((engId, index) ->
4. 4. train: {
5. 5. engineerId: engId
6. 6. }
7. 7. )
8. 8. }

C. 1. 1. trains:
2. 2. {(
3. 3. conductorIds map ((engId, index) ->
4. 4. train: {
5. 5. engineerId: engId
6. 6. }
7. 7. )
8. 8. )}

D. 1. 1. {( trains:
2. 2.
3. 3. conductorIds map ((engId, index) ->
4. 4. train: {
5. 5. engineerId: engId
6. 6. }
7. 7. )
8. 8. )}

C. 1. 1. trains:
2. 2. {(
3. 3. conductorIds map ((engId, index) ->
4. 4. train: {
5. 5. engineerId: engId
6. 6. }
7. 7. )
8. 8. )}

Explanation:
Points to remember:
* XML must have a root element.
* XML only allows one root element
* To avoid multiple root issues, you must create a root element for the XML output, whenever we transform output
* When mapping array elements (JSON or JAVA) to XML, wrap the map operations in {(..)}
-{ } are defining the object
( ) are transforming each element in the array as a key/value pair
* The transformation to XML would fail if the above mentioned considerations were not taken into account.
* Thus the transformation script declares a root element as trains and wraps the data in “{( )}“.
Whenever you see such type of question, always look out for root element followed by {( )} wrapping map.
I call this a "Wrap The Map" scenario. Hope it would help you remember !

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.

A company has an API to manage departments, with each department identified by a
unique deptld. The API was built with RAML according to MuleSoft best practices.
What is valid RAML to specify a method to update the details for a specific department?

A.

Option A

B.

Option B

C.

Option C

D.

Option D

D.

Option D

Refer to the exhibits. The Set Payload transformer in the addltem child flow uses DataWeave to create an order object. What is the correct DataWeave code for the Set Payload transformer in the createOrder flow to use the addltem child flow to add a router call with the price of 100 to the order?

A. lookup( "addltern", { price: "100", item: "router", itemType: "cable" } )

B. addltem( { payload: { price: "100", item: "router", itemType: "cable" > } )

C. lookup( "addltem", { payload: { price: "100", item: "router", itemType: "cable" } > )

D. addltem( { price: "100", item: "router", itemType: "cable" } )

C. lookup( "addltem", { payload: { price: "100", item: "router", itemType: "cable" } > )

How are query parameters dynamically passed to an outbound REST request using an HTTP Request operation?

A. As query parameters in the HTTP Request operation

B. As URI parameters in the HTTP Request operation

C. In the Mule event's payload

D. As flow variables

A. As query parameters in the HTTP Request operation

Explanation:
In General > Request > Query Parameters, click the plus icon (+) to add a parameter to a request. Type a name and value for the parameter or use a DataWeave expression to define the name and value.

Refer to the exhibit.

A. Option A

B. Option B

C. Option C

D. Option D

B. Option B

A Batch Job scope has five batch steps. An event processor throws an error in the second batch step because the input data is incomplete. What is the default behavior of the batch job after the error is thrown?

A. All processing of the batch job stops.

B. Event processing continues to the next batch step.

C. Error is ignored

D. Batch is retried

A. All processing of the batch job stops.

Explanation:
In case of an error , batch job completes in flight steps and stops further processing.
MuleSoft Doc Ref : Handling Errors During Batch Job | MuleSoft Documentation The default is all processing will stop but we can change it by Max Failed Record field.
General -> Max Failed Records: Mule has three options for handling a record-level error:
Finish processing, Continue processing and Continue processing until the batch job accumulates a maximum number of failed records. This behavior can be controlled by Max Failed Records.
The default value is Zero which corresponds to Finish processing.
The value -1, corresponds to Continue processing.
The value +ve integer, corresponds to Continue processing until the batch job accumulates a maximum number of failed records.

Refer to the exhibits.

The mule application is debugged in Anypoint Studio and stops at the breakpoint as shown in below exhibit.
What is the value of the payload displayed in the debugger at this breakpoint?

A. Start

B. Process

C. Finished

D. Payload is always empty at the breakpoint

A. Start

Correct answer is Start as that is the payload set before.