Which requirement would prevent Anypoint MQ from being used as the messaging broker for a Mule application?
A company is modernizing its legacy systems to speed access to applications and data while enabling adoption of new technologies. Unlocking the company’s systems and data is key to this business objective, including existing on-premises services that authorized external clients can access. The ГГ staff is primarily experienced only in supporting its legacy systems.
Given the current aggressive backlog and project-delivery requirements, the company wants to take a strategic approach during the first phase of its transformation projects by rapidly deploying APIs to Mule runtimes that can scale, connect to on-premises systems, and migrate when needed.
Following MuleSoft best practices, which MuleSoft runtime deployment option best meets the company’s goals for starting its digital-transformation journey?
Community Discussion
An airline is designing an API-led connectivity project to integrate its flight data with an online aggregation website. The connections must support secure communication, high performance, and asynchronous message exchange.
Which interface technologies are appropriate for the connectors in this integration, assuming MuleSoft fully supports these technologies and Anypoint Connectors exist for the interfaces?
Community Discussion
A Mule solution implements an Experience API and a System API as Mule applications that process messages in this sequence:
- The Experience API receives an Anypoint MQ request message (REQU) whose payload contains a variable-length list of request objects.
- The Experience API uses a For Each scope to split the list into individual objects and sends each object as a REQU_OBJECT message to an Anypoint MQ queue named REQUEST.
- The System API listens on the REQUEST queue, processes each message independently of every other message, and sends a response message to a response queue named RESPONSE_OBJECT. System API processing times can vary and are occasionally fairly long.
- The Experience API listens on the RESPONSE_OBJECT queue and receives, transforms, and accumulates every response.
- After it receives all responses corresponding to the original REQU message, the Experience API creates and publishes a response Anypoint MQ message (RESP) to an Anypoint MQ queue named RESPONSE. Its payload contains the list of responses returned by the System API, organized in the same order as the request objects originally sent in the REQU message.
Assume that successful response messages are returned by the Experience API to the RESPONSE queue for all REQU messages.
What is required for the Experience API to ensure that the object-list length and order in RESP match those in REQU, while also maximizing message throughput?
Community Discussion
An insurance company is designing a hybrid, load-balanced, single-cluster production runtime environment. To meet performance Service Level Agreement (SLA) objectives, it is considering running Mule applications in an active-active, multi-node cluster configuration.
What should be considered when operating its Mule applications in this type of environment?
Community Discussion
That's the end of the preview
It's free
Every verified question is free for all users.
No strings attached.

Community Discussion