Correct answer is Perform all communication involving service S synchronously from within the For

Each scope, so objects in RESP are in the exact same order as request objects in REQU : Using

Anypoint MQ, you can create two types of queues: Standard queue These queues don’t guarantee a

specific message order. Standard queues are the best fit for applications in which messages must be

delivered quickly. FIFO (first in, first out) queue These queues ensure that your messages arrive in

order. FIFO queues are the best fit for applications requiring strict message ordering and exactly-once

delivery, but in which message delivery speed is of less importance Use of FIFO queue is no where in

the option and also it decreased throughput. Similarly persistent object store is not the preferred

solution approach when you maximizing message throughput. This rules out one of the options.

Scatter Gather does not support ObjectStore. This rules out one of the options. Standard Anypoint

MQ queues don’t guarantee a specific message order hence using another for each block to collect

response wont work as requirement here is to ensure the order. Hence considering all the above

factors the feasible approach is Perform all communication involving service S synchronously from

within the For Each scope, so objects in RESP are in the exact same order as request objects in REQU

:

Correct answer is Create WSDL specification using text editor SOAP services are specified using

WSDL. A client program connecting to a web service can read the WSDL to determine what functions

are available on the server. We can not create WSDL specification in Design Center. We need to use

external text editor to create WSDL.

:

Reference: https://docs.mulesoft.com/mule-runtime/3.9/understanding-mule-configuration

:

* Anypoint Runtime Fabric is a container service that automates the deployment and orchestration

of your Mule applications and gateways.

* Runtime Fabric runs on customer-managed infrastructure on AWS, Azure, virtual machines (VMs)

or bare-metal servers.

* As none of the Mule applications use Mule domain projects. applications are not required to be

rewritten. Also when applications are deployed on RTF, by default ingress is allowed only on 8081.

* Hence port conflicts are not required to be managed by DevOps team

:

* Each Batch Job uses SEVERAL THREADS for the Batch Steps

* Each Batch Step instance receives ONE record at a time as the payload. It's not received in a block,

as it does not wait for multiple records to be completed before moving to next batch step. (So Option

D is out of choice)

* RECORDS are processed IN PARALLEL within and between the two Batch Steps.

* RECORDS are not processed in order. Let's say if second record completes batch_step_1 before

record 1, then it moves to batch_step_2 before record 1. (So option C and D are out of choice)

* A batch job is the scope element in an application in which Mule processes a message payload as a

batch of records. The term batch job is inclusive of all three phases of processing: Load and Dispatch,

Process, and On Complete.

* A batch job instance is an occurrence in a Mule application whenever a Mule flow executes a batch

job. Mule creates the batch job instance in the Load and Dispatch phase. Every batch job instance is

identified internally using a unique String known as batch job instance id.

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

Reference: https://blogs.mulesoft.com/dev-guides/api-security-ways-to-authenticate-and-authorize/