Correct answer is /accounts?account_type=retail&industry=finance

Query parameters are a defined set of parameters attached to the end of a url. They are extensions

of the URL that are used to help define specific content or actions based on the data being passed. To

append query params to the end of a URL, a ‘?’ Is added followed immediately by a query parameter.

To add multiple parameters, an ‘&’ is added in between each.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/MuleSoft_MCD-Level-1/page_61_img_2.jpg

:

Scatter-Gather sends the event to each routes concurrently. Hence both route in this example will

start in parallel. So total time to complete processing is 40 seconds

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.

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

:

:

Correct answer is

%dw 2.0

output application/json

import modules::Utility

---

Utility::encryptString( "John Smith" )

DataWeave 2.0 functions are packaged in modules. Before you begin, note that DataWeave 2.0 is for

Mule 4 apps. For Mule 3 apps, refer to DataWeave Operators in the Mule 3.9 documentation. For

other Mule versions, you can use the version selector for the Mule Runtime table of contents.

Functions in the Core (dw::Core) module are imported automatically into your DataWeave scripts. To

use other 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:

import dw::core::Strings

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

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.

For example, this import directive does not identify any functions to import from the String module,

so it calls the pluralize function like this: Strings::pluralize("box").

Transform

%dw 2.0

import dw::core::Strings

output application/json

---

{ 'plural': Strings::pluralize("box") }

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. Hence correct answer is option 2

:

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

: