MCD-Level-1 Exam Dumps - MuleSoft Certified Developer - Level 1 (Mule 4)

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

Correct answer is Nothing needs to be changed in the other APIs or their associated applications

This is the benefit of having separate interface layer. As there are no changes to interface , no changes are required on the API's which consumes this API in context

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 !

Option 2 is the correct answer as /api/* accespts everything starting with /api/

* Batch scope has filter criteria which says paylod mod 2 = 0 whch means only 2, 4 and 6 will be in batch scope.

* So payload for each of these will be incremented by 10.

* Aggregator has batch size defined as 2. So it will process in batch of two records.

* Hence option 3 is correct answer.

[20,40]

[60]

Behavior with aggregator configured with fixed size

In this scenario, the batch step sends the processed records to an aggregator, which starts processing the records and buffering them until the configured aggregator’s size is reached. After that, the aggregator sends the aggregated records to the stepping queue.

Diagram Description automatically generated

The batch job builds record blocks of the configured block size and sends them to their corresponding batch step for processing. Each batch step receives one or more record blocks and starts processing them in parallel. After the batch step processes a record, the batch step sends the record to the aggregator for further processing. The aggregator continues processing records until the number of aggregated records reaches the configured aggregator’s size.

https://docs.mulesoft.com/mule-runtime/4.3/batch-processing-concept