Exam MCIA - Level 1 All QuestionsBrowse all questions from this exam
Go to Exam
Question 86

An organization is designing an integration Mule application to process orders by submitting them to a back-end 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 back-end system. Orders that cannot be successfully submitted due to rejections from the back-end system will need to be processed manually (outside the back-end system).

The Mule application will be deployed to a customer-hosted runtime and is able to use an existing ActiveMQ broker if needed. The ActiveMQ broker is located inside the organization’s firewall. The back-end system has a track record of unreliability due to both 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 back-end system while supporting but minimizing manual order processing?

    Correct Answer: A

    To ensure the Mule application can handle unreliable network connections and system outages while minimizing manual order processing, the following combination is ideal: An Until Successful scope to call the back-end system ensures that retries are attempted until a request succeeds. This setup is crucial when dealing with intermittent issues but doesn't provide indefinite retries. ActiveMQ long-retry queues store failed messages and retry at intervals, providing a buffer against short-term issues. Finally, ActiveMQ dead-letter queues are used for messages that permanently fail, enabling manual processing of orders that can't be automatically submitted to the back-end system. This approach leverages the strengths of the Until Successful scope for handling retries and the robustness of ActiveMQ for managing messages and failures.

Discussion
ExamschafferOption: A

A is fine. ActiveMQ long-retry queue is ok since the message order isn't important (a failing message is scheduled to go to the tail of the original queue and redelivered to a message consumer); Until Successful scope to call the back-end system + One or more ActiveMQ dead-letter queues for manual processing +