In this case three configurations will be required each for port 8000, 6000 and 7000.

There would be three global elements defined for HTTP connections.

Each HTTP connection will have host and port. One example shown below with host as localhost and port 6000

Graphical user interface, application Description automatically generated

To use an HTTP listener, you need to declare a configuration with a corresponding connection. This declaration establishes the HTTP server that will listen to requests.

Additionally, you can configure a base path that applies to all listeners using the configuration.

< http:listener-config name= " HTTP_Listener_config " basePath= " api/v1 " >

< http:listener-connection host= " 0.0.0.0 " port= " 8081 " / >

< /http:listener-config >

https://docs.mulesoft.com/http-connector/1.6/http-listener-ref#http-listener-configuration

Sequence can be described as follows.

* When web client sends the request , it sends payload as Blue (mentioned in question)

* In first iteration this will go to default choice , which sets payload to Red

* Via default route , flow will call itself with payload as Red

* In second iteration , as payload is Red , it will go to first route in choice router which will set payload to Blk and second iteration will end returning back payload as Blk to first iteration.

* This Blk will be again set to payload and first iteration will end returning back response as Blk

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.

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

For Each Scope

The For Each scope splits a payload into elements and processes them one by one through the components that you place in the scope. It is similar to a  for-each / for  loop code block in most programming languages and can process any collection, including lists and arrays. The collection can be any supported content type, such as  application/json ,  application/java , or  application/xml .

General considerations about the For Each scope:

By default, For Each tries to split the payload. If the payload is a simple Java collection, the For Each scope can split it without any configuration. The payload inside the For Each scope is each of the split elements. Attributes within the original message are ignored because they are related to the entire message.

For Each does not modify the current payload. The output payload is the same as the input.

Mule Doc Reference :  https://docs.mulesoft.com/mule-runtime/4.3/for-each-scope-concept

API Exchange creates REST conenctor automtaically once API is published. Hence correct answer is Publish the API specification to Any point Exchange

Correct answer is Patients from year 2021.

The thing to note here is that year is not a query parameter and not the uri parameter. Hence it will filter all the patients and return the ones for whom year is 2021

Correct answer is 200.1234 as String {format: " .0# " } . Rest all options are not syntactically correct.

PUT replaces the original version of the resource, whereas the PATCH method supplies a set of instructions to modify the resource

Organization Administrators can approve/revoke/delete SLA tier access requests via API Manager only