Correct answer is ${training.host}

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

How to Configure Properties to Mule 4.X Platform?

1) Go to /src/main/resources project directory.

2) Create aconfiguration file with the name configuration.yaml inside the newly created config folder.

                                           Graphical user interface, application, Word Description automatically generated

3) Go To Project >  Global Element  > Create > General > select the configuration.yaml file create in step- 2)

                                             Graphical user interface, application Description automatically generated 

4) To verify develop a simple flow with HTTP listener which has above entries. Put the logger that prints the values on console.

                                               Graphical user interface, application Description automatically generated

5) Additional info: Similarly, when you want to access this port in DataWeave you need to use p function

                                              Graphical user interface, text, application, email Description automatically generated

Correct answer is as below.After all processing routes have finished execution, the Scatter-Gathercomponent creates a new Mule event that combines all resulting Mule events from each route, and then passes the new Mule event to the next component in the flow.

{

" 0 " : {

" attributes " : ...,

" payload " : " 100 "

},

" 1 " : {

" attributes " : ...,

" payload " : " 200 "

}

}

Bottom of Form

In case ofan 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

Choice router finds the FIRST true condition, then distribute the event to the ONE matched route.

MuleSoft Doc Ref: https://docs.mulesoft.com/mule-runtime/4.1/choice-router-concept

The Choice router dynamically routes messages through a flow according to a set of DataWeave expressions that evaluate message content. Each expression is associated with a different routing option. The effect is to add conditional processing to a flow, similar to an if/then/else code block in most programming languages.

Only one of the routes in the Choice router executes, meaning that the first expression that evaluates to true triggersthat route’s execution and the others are not checked. If none of the expressions are true, then the default route executes.

Diagram Description automatically generated

Lets revise few concepts RAML which can help us to find the answer of this question.

URI Parameters

Lets have a look at below example.

/foos:

/{id}:

/name/{name}:

Here, the braces { } around property names define URI parameters. They represent placeholders in each URI and donot reference root-level RAML file properties as we saw above in the baseUri declaration. The added lines represent the resources /foos/{id} and /foos/name/{name}.

Query Parameters

Now we ' ll define a way to query the foos collection using query parameters.Note that query parameters are defined using the same syntax that we used above for data types:

/foos:

get:

description:ListallFoosmatching query criteria,ifprovided;

otherwise list allFoos

queryParameters:

name?:string

ownerName?:string

Based on the above information , below is the only option which defines storeid as uri parameter and department as query parameter.

/{storeId}:

get:

queryParameter:

department: