MuleSoft MCD - Level 1 Practice Test - Questions Answers, Page 6

For Each Scope

The For Each scope splits a payload into elements and processes them one by one through the components that you place in the scope. It is similar to afor-each/forloop code block in most programming languages and can process any collection, including lists and arrays. The collection can be any supported content type, such asapplication/json,application/java, orapplication/xml.

General considerations about the For Each scope:

By default, For Each tries to split the payload. If the payload is a simple Java collection, the For Each scope can split it without any configuration. The payload inside the For Each scope is each of the split elements. Attributes within the original message are ignored because they are related to the entire message.

For Each does not modify the current payload. The output payload is the same as the input.

Mule Doc Reference :https://docs.mulesoft.com/mule-runtime/4.3/for-each-scope-concept

lookup(String, Any, Number)

This function enables you to execute a flow within a Mule app and retrieve the resulting payload.

It works in Mule apps that are running on Mule Runtime version 4.1.4 and later.

Similar to the Flow Reference component (recommended), the lookup function enables you to execute another flow within your app and to retrieve the resulting payload. It takes the flow's name and an input payload as parameters. For example, lookup('anotherFlow', payload) executes a flow named anotherFlow.

Correct answer is

lookup( 'createCustomerObject', {first: 'Aice, last: 'Green'})

MuleSoft Documentation Reference : https://docs.mulesoft.com/mule-runtime/4.3/dw-mule-functions-lookup

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.

Error in validation component will get processed by Processer level On Error Propagate block and then error will be rethrown which will get processed by flow level error handler which will set payload to 'Error- main flow'. Hence correct answer is Error - main flow

1) Request is received by HTTP listener

2) Try scope gets executed

3) The validator component in the Try scope creates an Error Object because the payload is not null.

4) The On Error Propagate handles the error. The payload is set to ''Error -- Try scope''

6) ''Error -- Try scope'' is returned to the 'On Error Continue' block. Main flow execution stops. Payload is set to 'Error - main flow'

7) ''Error - main flow'' is returned to the requestor in the body of the HTTP request. HTTP Status Code: 200

------------------------------------------------------------------------------------------------------------------------------------------

Reference Diagram though not exactly same, conditions are similar. They will help you answer any new question on error handling in real exam:

https://docs.mulesoft.com/mule-runtime/4.3/on-error-scope-concept#on-error-continue

The HTTP 415 Unsupported Media Type client error response code indicates that the server refuses to accept the request because the payload format is in an unsupported format. The format problem might be due to the request's indicated Content-Type or Content-Encoding , or as a result of inspecting the data directly. In this case as per RAML specification data is expected in application/json and in request Content-Type is set as 'text/plain' which is incorrect. Hence solution is set the request Content-Type header to application/json

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/415

This is a trcik question. On complete phase pyalod consists of summary of records processed which gives insight on which records failed or passed. Hence option 4 is correct answer

MuleSoft Documentation Reference : https://docs.mulesoft.com/mule-runtime/4.3/batch-processing-concept#on-complete

Correct answer is APP: API RESOURCE NOT FOUND

---------------------------------------------------------------------------------------------------------------------------------------------------

1) A web client submits the request to the HTTP Listener.

2) The HTTP Request throws an 'HTTP:NOT_FOUND' error, execution halts.

3) The On Error Propagate error Handler handles the error. In this case ,HTTP:NOT_FOUND error is mapped to custom error APP:API_RESOURCE_NOT_FOUND. This error processor sets payload to APP:API_RESOURCE_NOT_FOUND.

4) ''APP:API_RESOURCE_NOT_FOUND. '' is the error message returned to the requestor in the body of the HTTP request with HTTP Status Code: 500

Reference Diagram: