nerdexam
IBM

C2180-274 · Question #37

The solution implementer configured a multi-protocol gateway (MPGW) service to process WebSphere MQ messages using the same MQ queue manager object for both the front end and back end. A request…

The correct answer is C. Configure "Units of Work = 1" and "Automatic Backout = on"; "Backout Threshold" and "Backout. See the full explanation below for the reasoning.

Question

The solution implementer configured a multi-protocol gateway (MPGW) service to process WebSphere MQ messages using the same MQ queue manager object for both the front end and back end. A request rule in the processing policy sends a message to queue A and then to queue B in a single transaction by using a "Result Action". The MQ URL for the back end contains the "Transactional=true" tag. The output type of the "Result Actions" is set as "Binary" and the OUTPUT context has a named variable. What are the additional configuration options that the solution implementer needs to guarantee message delivery for both back-end queues? Specifically, if any one message fails, the entire transaction will roll back.

Options

  • AConfigure two phase commit in the backend WebSphere MQ queue manager.
  • BConfigure "Units of Work = 1" and "Automatic Backout = off " in the MQ queue manager object.
  • CConfigure "Units of Work = 1" and "Automatic Backout = on"; "Backout Threshold" and "Backout
  • DDataPower cannot support this use case as an MQ queue manager object only works with global

How the community answered

(45 responses)
  • A
    7% (3)
  • B
    4% (2)
  • C
    73% (33)
  • D
    16% (7)

Community Discussion

No community discussion yet for this question.

Full C2180-274 Practice