When performing backup and recovery of an IBM MQ queue manager in a production environment, which approach ensures minimal downtime and complete restoration of messages, subscriptions, and configurations in case of system failure?

• A. Using MQ's in-built backup utilities or taking a filesystem-level backup of the queue manager's data directory including logs and journal files
• B. Copying only the queue manager configuration files without messages
• C. Relying solely on client-side message logs
• D. Cloning the queue manager on a different server without stopping the active instance

In distributed environments, IBM MQ must prevent message duplication during delivery. Which feature ensures that once a message is successfully delivered and acknowledged, it is not reprocessed by the receiver in case of retries?

• A. Automatic channel restarts with unlimited retries
• B. Channel sequence numbers and persistent storage tracking
• C. Multiple receivers bound to the same queue
• D. Non-persistent messages being discarded after transmission

Security in IBM MQ can be implemented using several mechanisms. Which method specifically ensures that administrators can restrict access so that only authorized applications or users can put or get messages from specific queues?

• A. SSL encryption on message payloads
• B. Queue-level object authority manager (OAM) permissions
• C. Channel exit routines written in custom code
• D. Clustering configuration for workload balancing

In IBM MQ architecture, when an application sends a persistent message that must survive system restarts and power failures, which internal mechanism ensures that the message is not lost until it is delivered successfully?

• A. Message is logged to recovery logs and queue files for durability
• B. Message is stored in the Dead Letter Queue by default until the system restarts
• C. Message is written only to memory cache and flushed when resources are freed
• D. Message is duplicated in multiple queues across different queue managers

How does IBM MQ ensure transactional integrity when a message needs to be sent to multiple queues or multiple resource managers as part of a single business operation, and which mechanism coordinates the commit process to maintain atomicity across distributed systems?

• A. Local transactions that apply only to a single queue and cannot coordinate across multiple resources.
• B. Non-persistent messaging that provides faster delivery but does not guarantee transactional integrity.
• C. Clustering that replicates messages to all queue managers to maintain consistency.
• D. Two-phase commit using XA transactions that coordinate the commit across multiple queues and resource managers to ensure all-or-nothing execution.