IBM WebSphere MQ V7.0, System Administration - C2180-374 FREE EXAM DUMPS QUESTIONS & ANSWERS

Each of the queue manger QM1, QM2 and QM4 has an instance of cluster queue CLUS_Q Channels TO.QM1,TO.QM2, TO.QM3 and TO.QM4 are defined on each queue manager, respectively. The following MQSC commands are issued.
On QM1:
ALTER CHL (TO.QM1) CHLTYPE (CLUSRCVR) CLWLRANK (1)
ALTER QL(CLUS_Q) CLWRANK (3) ?CHLWLUSEQ (ANY)
On QM2:
ALTER CHL (TO.QM2) CHLTYPE (CLUSRCVR) CLWLRANK (3)
ALTER QL(CLUS_Q) CLWRANK (2) ?CHLWLUSEQ (ANY)
On QM3:
ALTER CHL (TO.QM3) CHLTYPE (CLUSRCVR) CLWLRANK (3)
ALTER QL(CLUS_Q) CLWRANK (1) ?CHLWLUSEQ (ANY)
On QM3:
ALTER CHL (TO.QM4) CHLTYPE (CLUSRCVR) CLWLRANK (2)
ALTER QL(CLUS_Q) CLWRANK (3) ?CHLWLUSEQ (ANY)
To which queue manager will the messages be delivered after these changes?

The administrator wants to define a service object on a queue manager on Windows so that an application will start when the queue manager is started and stop when the queue manager is stopped. What attribute should the administrator include on the DEFINE SERVICE command inrunmqsc to ensure that this happens?

An IBM WebSphere MQ client application puts messages onto remote queue RQ on queue manager QM1, which resolves to the local queue LQ on queue manager QM2. A new version of the application has been deployed that has the capability to put messages greater than 4MB. The administrator changed the max message length attributes for the queue managers, transmission queue, sender-receiver channels and LQ to handle the larger messages. The administrator was later notified that messages greater than 4MB are still not reaching LQ. The most likely cause of the problem is the max message length attribute:

An administer wants to use the MCAUSER field in the server-connection channel definition to control access by the client application.
This can be achieved by setting MCAUSER to:

Queue managers QMGR1 and QMGR2 are members of cluster QMCLUS. An application connected to QMGR1 needs to send messages to a local queue APP.LOCAL of QMGR2. The administrator creates the following definitions: On QMGR1: DEFINE QALIAS(APP.ALIAS) + TARGET(APP.LOCAL) + CLUSTER(QMCLUS) On QMGR2: DEFINE QLOCAL(APP.LOCAL) + MAXDEPTH(50000) The administrator is notified that the application is unable to send messages to APP.LOCAL. What is the most likely cause?

What object must be running to handle inbound connection requests to start receiver channels?

Queue manager QMGR1 and QMGR2 are connected by sender receiver channels. An application puts messages on a remote queue of QMGR1 that are then delivered to a local queue of QMGR2.
The administrator is notified that messages are not reaching their destination on queue manager QMGR2 and notices that the queue depth of the transmission queue is increasing on QMGR1.
Why aren't messages reaching QMGR2?

An administrator has been asked to create MQ objects on queue manager QM1 so that applications connecting to queue manager QM1 can send messages to queue PAYROLL on queue manger QM2. The following definitions have been created on QM2:
DEFINE QLOCAL (PAYROLL) REPLACE PUT (ENABLED) GET (ENABLED) +
DESCR ('Local queue for QM1 payroll details')
DEFINE CHANNEL (QM1.TO.QM2) CHLTYPE (RCVR) TRPTYPE (TCP) +
REPLACE DESCR ('Receiver channel from QM1')
What are the minimum definitions needed on QM1?

An administrator wants to control access to queue Q1 QMGR1. User ID user1 have MQPUT access only, and group ID grp1 should have MQGET access only.
Which of the following commands can achieve this?

QM2 and its objects have been recreated using the save queue manager definitions. The sender channel on queue manager QM1 is in retry status with an error message AMQ9526: Message sequence number error for channel 'QM1.TO.QM2'. Which action will recover the channel?

A queue manager QM1 on UNIX has an unrecoverable problem. The IBM Support Center has asked the administrator to send any FFST reports. Which directory can an administrator get these FFST files from?