Certified MuleSoft Integration Architect IDemo

By Salesforce · Question Mode

QuestionQ15

MuleSoft application network concepts

A stock-trading company processes millions of trades per day and requires outstanding performance and reliability from its stock-trading system. The company runs several event-driven APIs, implemented as Mule applications, on various customer-hosted Mule clusters, and must enable message exchanges among the APIs on its internal network through shared message queues.

What is an effective approach for satisfying the event-driven APIs’ cross-cluster messaging requirements?

  • A eXtended Architecture (XA) transactions and XA connected components with manual acknowledgements
  • B Persistent VM queues with automatic acknowledgements
  • C JMS transactions with automatic acknowledgements
  • D Non-transactional JMS operations with a reliability pattern and manual acknowledgements
Explanation

A shared JMS broker can be accessed by Mule applications on separate clusters. JMS transactions acknowledge consumed messages and commit published messages only when the transaction succeeds; if processing fails and the transaction rolls back, the message remains available for redelivery. This provides reliable cross-cluster messaging without the added coordination cost of XA transactions.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!