* 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
