Master the MuleSoft Certified Developer - Level 1 (Mule 4) MCD-Level-1 Exam with Confidence!

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 a for-each/for loop code block in most programming languages and can process any collection, including lists and arrays. The collection can be any supported content type, such as application/json, application/java, or application/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

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. As per RAML input is expected in application/xml.

Hence correct answer is Set a request header with the name Content-Type to a

* To use custom 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:

1) Does not identify any functions to import from the String module:

import dw::core::Strings

2) To identify a specific function to import from the String module:

import camelize, capitalize from dw::core::Strings

3) To import all functions from the String module:

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.

* In given scenario, it's mentioned to import all of the WebStore.dwl

So correct answer is:

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:

Timeline Description automatically generated

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

Correct answer is Array.

Flatten turns a set of subarrays (such as [ [1,2,3], [4,5,[6]], [], [null] ]) into a single, flattened array (such as [ 1, 2, 3, 4, 5, [6], null ]).

This example defines three arrays of numbers, creates another array containing those three arrays, and then uses the flatten function to convert the array of arrays into a single array with all values.

Source

%dw 2.0

output application/json

var array1 = [1,2,3]

var array2 = [4,5,6]

var array3 = [7,8,9]

var arrayOfArrays = [array1, array2, array3]

---

flatten(arrayOfArrays)

Output

[ 1,2,3,4,5,6,7,8,9 ]

WSDL is used to define the contract in case of SOAP . RAML/OAS is used to REST services