IBM API Connect, as part of IBM Cloud Pak for Integration (CP4I), supports various deployment topologies, including Active/Active and Active/Passive configurations across multiple data centers. Let's analyze the provided topology carefully:
Backup Strategy (Option A - Correct)
The API Manager and Developer Portal components are stateful and require regular backups.
Since the topology spans across two sites, these backups should be replicated to the second site to ensure disaster recovery (DR) and high availability (HA).
This aligns with IBM’s best practices for multi-data center deployment of API Connect.
Deployment Mode for API Manager & Portal (Option B - Incorrect)
The question suggests that API Manager and Portal are deployed across two sites.
If it were an Active/Passive deployment, only one site would be actively handling requests, while the second remains idle.
However, in IBM’s recommended architectures, API Manager and Portal are usually deployed in an Active/Active setup with proper failover mechanisms.
Cluster Type (Option C - Incorrect)
A distributed Kubernetes cluster across multiple sites would require an underlying multi-cluster federation or synchronization.
IBM API Connect is usually deployed on separate Kubernetes clusters per data center, rather than a single distributed cluster.
Therefore, this topology does not represent a distributed Kubernetes cluster across sites.
Failover Behavior (Option D - Incorrect)
Kubernetes cannot automatically detect failures in Data Center 1 and migrate services to Data Center 2 unless specifically configured with multi-cluster HA policies and disaster recovery.
Instead, IBM API Connect HA and DR mechanisms would handle failover via manual or automated orchestration, but not via Kubernetes native services.
Gateway and Analytics Deployment (Option E - Correct)
API Gateway and Analytics services are typically deployed in Active/Active mode for high availability and load balancing.
This means that traffic is dynamically routed to the available instance in both sites, ensuring uninterrupted API traffic even if one data center goes down.
Final Answer:✅ A. Regular backups of the API Manager and Portal have to be taken, and these backups should be replicated to the second site.✅ E. This represents an Active/Active deployment for Gateway and Analytics services.
