Exam MCIA - Level 1 All QuestionsBrowse all questions from this exam
Question 18

Refer to the exhibit. A Mule 4 application has a parent flow that breaks up a JSON array payload into 200 separate items, then sends each item one at a time inside an Async scope to a VM queue.

A second flow to process orders has a VM Listener on the same VM queue. The rest of this flow processes each received item by writing the item to a database.

This Mule application is deployed to four CloudHub workers with persistent queues enabled.

What message processing guarantees are provided by the VM queue and the CloudHub workers, and how are VM messages routed among the CloudHub workers for each invocation of the parent flow under normal operating conditions where all the CloudHub workers remain online?

    Correct Answer: A

    Each item VM message is processed at least once by one arbitrary CloudHub worker. Given the design of Mule 4 applications and the use of CloudHub with persistent queues, the messages from the VM queue are not bound to the worker where the message was produced. Instead, the messages are distributed among the available workers. Therefore, each worker can be expected to process some of the VM messages, ensuring load distribution and reliability across the workers.

Discussion
Pavan_NagineniOption: A

A. EACH item VM message is processed AT LEAST ONCE by ONE ARBITRARY CloudHub worker Each of the four CloudHub workers can be expected to process some item VM messages CLoudhub your app workers would be sharing OSV2 and VM queues space by not being with cluster But some other ways

awstjOption: A

A is the answer

sanni27Option: A

It should be A

Outdoor25Option: D

It should be D. Persistent VM queues in Cloudhub are meant to distribute load across different workers. https://help.mulesoft.com/s/article/CloudHub-Persistent-Queues-Explained

majda091983

yes but not on a deterministic round-robin fashion

Viv2005Option: A

Why D is not the right answer? Because persistent queues do not guarantee one-time delivery i.e messages can be duplicated. Though it is true that traffic will be load balanced for VM listeners but there is no document that says it is a deterministic round-robin.

awsuser1Option: A

A is correct answer

anonymouse69420Option: A

https://help.mulesoft.com/sfc/servlet.shepherd/version/renditionDownload?rendition=THUMB720BY480&versionId=0682T000003zVkE&operationContext=CHATTER&contentId=05T2T00000G1WXS&page=0

tchine88Option: C

the right answer is C, because by default the VM queue is an in memory queue, so all items will be processed in the same worker

bkahramanOption: A

D cannot be because of undeterministic distribution

majda091983Option: A

explication from Mule doc : When running a Mule application in single runtime instance mode, persistent queues work by serializing and storing the contents on the disk. However, when running the Mule application in cluster runtime instance mode, the persistent queues are backed up in the memory grid. Thereby, when a flow uses VM Connector to publish content to a queue, Mule runtime engine determines whether to process the message in the same origin node or to send the message to the cluster to pick another node. Using VM Connector facilitates the load distribution across a cluster.

majda091983Option: A

answer is A

madgeezerOption: A

A. EACH item VM message is processed AT LEAST ONCE by ONE ARBITRARY CloudHub worker Each of the four CloudHub workers can be expected to process some item VM messages Persistent Queue means all workers share the memory so it could processed by more than one worker

AkanshaR91Option: D

At MOST once. Should be D

[Removed]Option: A

should be A, point to be noted is we are using a persistent queue over here, which means all the workers share the same memory for the queue, it might be possible another worker would pickup msg from the queue

razz123098Option: A

A is the answer