An integration Mute application is being designed to process orders by submitting them to a backend system for offline processing. Each order will be received by the Mute 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 Non-persistent VM ActiveMQ Dead Letter Queue for manual processing
B . An On Error scope MuleSoft Object Store ActiveMQ Dead Letter Queue for manual processing
C . Until Successful component MuleSoft Object Store ActiveMQ is NOT needed or used
D . Until Successful component ActiveMQ long retry Queue ActiveMQ Dead Letter Queue for manual processing
Answer: D
Leave a Reply