IBM WebSphere MQ V7.0, Solution Design Sample Questions:

1. A solution depends on messages being dropped during a queue manager restart. These messages are defined as nonpersistent. After a queue manager restarts, the solution designer notes that the messages were not dropped as expected but got processed. Which one of the following options is the likely cause?

A) The messages reside on a z/OS shared queue
B) The application has not set persistence, and the default persistence at the QMGR level isDEFPSIST(YES)
C) The application is putting the messages to a QALIAS with DEFPSIST(NO), however the targetqueue has DEFPSIST(YES) set
D) The application is using permanent dynamic queues

2. An application is experiencing issues when processing large volumes of nonpersistent messages.
Which of the following is a likely cause of the issue?

A) The BATCHSIZE parameter on the queuemanager was left at the default setting.
B) The application is processing in syncpoint, and has not performed a commit recently.
C) The WebSphere MQ linear logs are not large enough to handle all of the transactions.
D) The WebSphere MQ circular logs are not large enough to handle all of the transactions.

3. A WebSphere MQ client application is sending messages to a central server which will later be processed in batch. Given that all information is stored only in a central location, what is the best way of designing such communication? The application:

A) sends updates and the server should send acknowledgement messages. The applicationshould wait for them in a separate thread.
B) sends updates and the server should send acknowledgement messages. The applicationshould wait for them in the same thread that sent the update messages.
C) publishes the messages to a topic defined by the server application.
D) puts messages to a server queue, and no acknowledgement from the central application isrequired.

4. Business owners want to allow an existing application to be easily portable to any of four Linux servers in their data center. For this they want the four queue managers on these servers to be changed to have the same name. What must be the response of the WebSphere MQ Solution Designer?

A) It cannot be done. All interconnected queue managers must have unique names.
B) There is no problem.
C) It is possible to define queue managers with identical names in a network, but it is not recommended.
D) Queue managers cannot be renamed, so this can only be done by recreating the queue managers. Beyond that, there is no problem.

5. A company is porting a solution written in C to i5/OS (successor to OS/400) that will send orders to the Order Processing system, which is a WebSphere MQ application on z/OS. Which of the following configurations for the new solution on i5/OS provides the function needed for this scenario? The solution on i5/OS would run:

A) only as a server, using the WebSphere MQ server on i5/OS to access the Order Processingsystem.
B) as a client or full server, using either the WebSphere MQ client or a full WebSphere MQ serveron i5/OS to access the Order Processing system.
C) only as a client, using the WebSphere MQ client on i5/OS to access the Order Processingsystem.
D) as a standalone application, accessing a WebSphere MQ-enabled adapter on the mainframeto access the Order Processing system.

Solutions: