In IBM Cloud Pak for Integration (CP4I) v2021.2, when deploying a highly available single-resilient queue manager, storage considerations are crucial to ensuring fault tolerance and failover capability.
A single-resilient queue manager uses a shared file system that allows different queue manager instances to access the same data, enabling failover to another node in the event of failure. The key requirement is data write integrity, ensuring that only one instance has access at a time and that locks are properly released in case of a node failure.
Option A is correct: A shared file system must support data consistency and failover mechanisms to ensure that only one instance writes to the queue manager logs and data at any time. If the active instance fails, another instance can take over using the same storage.
Option B is incorrect: While cloud storage replication across availability zones is useful, it does not replace the need for a proper shared file system with write integrity.
Option C is incorrect: Persistent volumes are supported for resilient queue managers when deployed in Kubernetes environments like OpenShift, as long as they meet the required file system properties.
Option D is incorrect: A single resilient queue manager can recover quickly by failing over to a standby node, often faster than a multi-instance queue manager, which requires additional failover processes.
IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References:
IBM MQ High Availability Documentation
IBM Cloud Pak for Integration Storage Considerations
IBM MQ Resiliency and Disaster Recovery Guide
Submit