Which queue manager includes a pair of pods, one of which is the active queue...

In IBM Cloud Pak for Integration (CP4I) v2021.2, IBM MQ provides multiple high-availability (HA) deployment options. A multi-instance queue manager consists of a pair of pods:

One active queue manager (handling message processing).

One standby queue manager (ready to take over if the active instance fails).

The standby instance continuously monitors the active queue manager, and if it detects a failure, it automatically takes over, ensuring minimal downtime and high availability.

A. Native HA – Incorrect

Native HA (Highly Available) queue managers use persistent storage and multiple replicas for redundancy but do not rely on an active-standby pod setup. Instead, they use Raft consensus for leader election and failover.

They are different from multi-instance queue managers, which explicitly have one active and one standby pod.

C. Single Resilient – Incorrect

A Single Resilient queue manager has only one instance running and recovers using persistent storage, but it does not have a standby pod for immediate failover.

D. Replicated Data – Incorrect

"Replicated Data" is not a specific IBM MQ HA mode. Instead, Native HA queue managers use replicated data across multiple pods to ensure resilience.

Why the other options are incorrect:

IBM MQ Multi-Instance Queue Manager Documentation

IBM Cloud Pak for Integration – High Availability Configurations

OpenShift Deployment of IBM MQ

IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References: