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.

An object store is a facility for storing objects in or across Mule applications. Mule runtime engine (Mule) uses object stores to persist data for eventual retrieval. Internally, Mule uses object stores in various filters, routers, and other message processors that need to store states between messages.

Object stores are available in all deployment targets. If you deploy your application to CloudHub, you can also use Object Store V2.

Correct answer is Key/value pair in Object store

MuleSoft Documentation reference : https://docs.mulesoft.com/mule-runtime/4.3/mule-object-stores#use-cases

Correct answer is Change the method attributes value to " POST " .

It can be fixed in either of the two ways as below.

1) Changing method attribute to POST in ClientRequestFlow

2) Setting allowedMethods as PUT in ShippingFlow (but doesn ' t fit as question mentions about changing ClientRequestFlow)

Entire event would be sent to each route in parallel.

Scatter-Gather works as follows :

- The Scatter-Gather component receives a Mule event and sends a reference of this Mule event to each processing route.

- Each of the processing routes starts executing in parallel. After all processors inside a route finish processing, the route returns a Mule event, which can be either the same Mule event without modifications or a new Mule event created by the processors in the route as a result of the modifications applied.

- After all processing routes have finished execution, the Scatter-Gather component 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.

Diagram Description automatically generated

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.

Correct syntax to use where clause is  WHERE city = :city AND state = :state

This question validates knowledge on using dynamic queries in DB select operation.

Configure Dynamic Queries in the Select Operation

When you need to parameterize not only the  WHERE  clause but also parts of the query itself (for example, queries that compare tables that depend on a condition, or complex queries for which the project table columns need to vary), you can configure dynamic queries.

In the following example, you configure a dynamic query by using a full expression with a string in which the table depends on a variable  $(vars.table) . Although some of the query text is dynamic ( " SELECT * FROM $(vars.table) ), the  WHERE  clause still defines the  WHERE  condition using input parameters: in this case,  WHERE name = :name .

In your Studio flow, select the  Select  operation.

In the operation configuration screen, set the  SQL Query Text  field to  SELECT * FROM $(vars.table) WHERE name = :name .

Set the  Input Parameters  field to  { ' name ' : payload} .

The following screenshot shows the configuration in Studio:

Graphical user interface, application Description automatically generated

Figure 3. Dynamic query configuration

In the XML editor, the  < db:sql >  configuration looks like this:

< set-variable variableName = " table " value = " PLANET " / >

< db:select config-ref = " dbConfig " >

< db:sql > #[ " SELECT * FROM $(vars.table) WHERE name = :name " ] < /db:sql >

< db:input-parameters >

#[{ ' name ' : payload}]

< /db:input-parameters >

< /db:select >

You can apply input parameters only to parameters in a  WHERE  clause. To modify any other part of the query, use the DataWeave interpolation operator.

Mule Ref Doc:  Query a Database Examples - Mule 4 | MuleSoft Documentation

Correct Answer: Response body: " Error " Default response status code: 200.

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

1) Payload is successfully set to “Success – Started Flow”

2) When HTTP Request throws an error, execution halts

#[error.description] = “ABC "

#[error.errorType] = " XYZ "

3) The On Error Continue scope handles the error. When On Error Continue scope is invoked, all the processors in error block are executed and success response is sent back to the client with payload which is set in error flow. In this case payload is set to " Error " value in error block.

4) “Error” is returned to the requestor in the body of the HTTP request with HTTP Status Code: 200 as On error continue always sends success error code.

Reference Diagram:

Timeline Description automatically generated with medium confiden ce