IBM
C2180-376 · Question #101
The WebSphere MQ client interface is popular in part because the client software is free, but this is offset by a number of functional limitations. When deciding whether to deploy an application…
The correct answer is D. Transactional processing with local units of work is not supported. See the full explanation below for the reasoning.
Question
The WebSphere MQ client interface is popular in part because the client software is free, but this is offset by a number of functional limitations. When deciding whether to deploy an application with the client interface or with a local queue manager, these must be considered. Which of the following is NOT a limitation of the WebSphere MQ client?
Options
- AClients cannot be centrally managed by WebSphere MQ tooling.
- BIn the event of a network outage it can be difficult to determine if the last API call was actually
- CData cannot be stored as messages by the client in the event of network outages.
- DTransactional processing with local units of work is not supported.
How the community answered
(17 responses)- A6% (1)
- B12% (2)
- C6% (1)
- D76% (13)
Community Discussion
No community discussion yet for this question.