Certified MuleSoft Developer I Dumps PDF Free Download

QUESTION: 41

A web client submits a request to http://localhost:8081?accountType=personal. The query parameter is captured using a Set Variable transformer to a variable named accountType.
What is the correct DataWeave expression to log accountType?

Account Type: #[flowVars.accountType]
Account Type: #[message.inboundProperties.accountType]
Account Type: # [attributes.accountType]
Account Type: #[vars.accountType]

Answer(s): D

Explanation:

vars: Keyword for accessing a variable, for example, through a DataWeave expression in a Mule component, such as the Logger, or from an Input or Output parameter of an operation. If the name of your variable is myVar, you can access it like this: vars.myVar Hence correct answer is Account Type: #[vars.accountType]

Reveal Solution Next Question

QUESTION: 42

Refer to the exhibit. The Batch Job processes, filters and aggregates records, What is the expected output from the Logger component?

[10. 20, 30. 40, 50, 60]
[10. 20] [30, 40] [50, 60]
[20, 40, 60]
[20. 40] [60]

Answer(s): D

Explanation:

* 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.

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

Reveal Solution Next Question

QUESTION: 43

Refer to the exhibits.

A web client submits a request to http://localhQst:8081.
What is the structure of the payload at the end of the flow?
A)

B)

C)

D)

Option A
Option B
Option C
Option D

Answer(s): D

Explanation:

Scatter-Gather Router
The Scatter-Gather component is a routing event processor that processes a Mule event through different parallel processing routes that contain different event processors. Each route receives a reference to the Mule event and executes a sequence of one or more event processors. Each of these routes uses a separate thread to execute the event processors, and the resulting Mule event can be either the same Mule event without modifications or a new Mule event with its own payload, attributes, and variables. The Scatter-Gather component then combines the Mule events returned by each processing route into a new Mule event that is passed to the next event processor only after every route completes successfully.
The Scatter-Gather component executes each route in parallel, not sequentially. Parallel execution of routes can greatly increase the efficiency of your Mule application and may provide more information than sequential processing.

Reference:

https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept

Reveal Solution Next Question

QUESTION: 44

Refer to the exhibits. A web client submits a request to http://localhost:8081/fliqhts?destination=SFO and the Web Service Consumer throws a WSC:BAD_REQUEST error.
What is the next step to fix this error?

Set a header In the Consume operation equal to the destination query parameter
set a SOAP payload before the Consume operation that contains the destination query parameter
set a property m the Consume operation equal to the destination query parameter
set a JSON payload before the Consume operation that contains the destination query parameter

Answer(s): B

Explanation:

As can be seen in error message , SOAP service findFlights expects the SOAP paylaod. This can be set using transform message processor which forms SOAP payload before the Consume operation that contains the destination query parameter

Reveal Solution Next Question