Exam MCIA - Level 1 topic 1 question 15 discussion

Actual exam question from Mulesoft's MCIA - Level 1

Question #: 15
Topic #: 1

An integration Mule application is being designed to process orders by submitting them to a backend system for offline processing. Each order will be received by the Mule application through an HTTPS POST and must be acknowledged immediately. Once acknowledged, the order will be submitted to a backend system.
Orders that cannot be successfully submitted due to rejections from the backend system will need to be processed manually (outside the backend system).
The Mule application will be deployed to a customer-hosted runtime and is able to use an existing ActiveMQ broker if needed.
The backend system has a track record of unreliability both due to minor network connectivity issues and longer outages.
What idiomatic (used for their intended purposes) combination of Mule application components and ActiveMQ queues are required to ensure automatic submission of orders to the backend system, while minimizing manual order processing?

A. An On Error scope MuleSoft Object Store ActiveMQ Dead Letter Queue for manual processing
B. Until Successful component ActiveMQ long retry Queue ActiveMQ Dead Letter Queue for manual processing
C. Until Successful component MuleSoft Object Store ActiveMQ is NOT needed or used
D. An On Error scope Non-persistent VM ActiveMQ Dead Letter Queue for manual processing

Show Suggested Answer

Suggested Answer: B 🗳️

by Rahul1387 at July 22, 2021, 1:40 a.m.

Comments

Submit Cancel

edogwest

3 months ago

Selected Answer: B

Idiomatic pattern for reliability problems. • Until Successful keeps the HTTP-listener thread free (the message is already acknowledged) and handles quick, transient “blips”. • If the backend is down for hours, the flow can route the message to a long-retry queue with a scheduled redelivery delay—letting the broker, not Mule memory, hold the backlog safely. • When retries are exhausted or the backend functionally rejects the order, the message is sent to a DLQ, providing a clean hand-off for manual processing.

upvoted 1 times

...

RegTheB

4 months, 3 weeks ago

Selected Answer: B

Until Successful component ActiveMQ long retry Queue ActiveMQ Dead Letter Queue for manual processing

upvoted 1 times

...

vikas_mule

11 months, 3 weeks ago

B, combination of Mule application components and ActiveMQ queues are required to ensure automatic submission of orders to the backend system, while minimizing manual order processing, until succesful is an automatic submission of order

upvoted 1 times

...

madgeezer

2 years, 5 months ago

Selected Answer: B

B. Until Successful component ActiveMQ long retry Queue ActiveMQ Dead Letter Queue for manual processing

upvoted 1 times

...

sanni27

3 years ago

should be B

upvoted 2 times

...

Outdoor25

3 years, 1 month ago

Should be B. Retries are needed as well as manual processing ability of order without loosing any orders. D involves non persistant VM, however does not describe how message ends up in ActiveMQ DLQ. Typically message ends up in DLQ after a message dequeue has failed x number of times due to transaction roll back or other reasons.

upvoted 3 times

...

Pavan_Nagineni

3 years, 5 months ago

B. Until Successful component ActiveMQ long retry Queue ActiveMQ Dead Letter Queue for manual processing

upvoted 2 times

...

Rahul1387

3 years, 6 months ago

It should be B. Until successful and dead letter queue

upvoted 3 times

...