C1000-130 Exam Dumps : IBM Cloud Pak for Integration V2021.2 Administration

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.

IBM API Connect Deployment Topologies

IBM Documentation – API Connect Deployment Models

High Availability and Disaster Recovery in IBM API Connect

IBM API Connect HA & DR Guide

IBM Cloud Pak for Integration Architecture Guide

IBM Cloud Pak for Integration Docs

References:

When installing IBM Cloud Pak for Integration (CP4I) on an OpenShift cluster that lacks internet access, an air-gapped installation is required. This process involves mirroring container images from an IBM container registry to a portable registry that can be accessed by the disconnected OpenShift cluster.

To authenticate and mirror images, the administrator must:

Use the cloudctl case command to configure credentials, including the IBM entitlement key, before initiating the mirroring process.

Authenticate with the IBM Container Registry using the entitlement key.

Mirror the required images from IBM’s registry to a local registry that the disconnected OpenShift cluster can access.

B. export ENTITLEMENTKEY and cloudPakOfflineInstaller -mirror-images

The command cloudPakOfflineInstaller -mirror-images is not a valid IBM Cloud Pak installation step.

IBM requires the use of cloudctl case commands for air-gapped installations.

C. Adding the entitlement key to .airgap/registries

There is no documented requirement to store the entitlement key in SHOME/.airgap/registries.

IBM Cloud Pak for Integration does not use this file for authentication.

D. Adding the ibm-entitlement-key as a Docker secret

While secrets are used in OpenShift for image pulling, they are not directly involved in mirroring images for air-gapped installations.

The entitlement key is required at the mirroring step, not when deploying the images.

Why Other Options Are Incorrect:IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References:

IBM Documentation: Installing Cloud Pak for Integration in an Air-Gapped Environment

IBM Cloud Pak Entitlement Key and Image Mirroring

OpenShift Air-Gapped Installation Guide

In an IBM Cloud Pak for Integration (CP4I) v2021.2 deployment, certain components require ReadWriteMany (RWX) storage to allow multiple pods to read and write data concurrently.

CouchDB is used as the Asset Repository in CP4I to store configuration and metadata for IBM Automation Assets.

It requires persistent storage that can be accessed by multiple instances simultaneously.

RWX storage is necessary because multiple pods may need concurrent access to the same database storage in a distributed deployment.

Common RWX storage options in OpenShift include NFS, Portworx, or CephFS.

Why Option B (CouchDB for Asset Repository) is Correct:

A. MQ multi-instance → Incorrect

IBM MQ multi-instance queue managers require ReadWriteOnce (RWO) storage because only one active instance at a time can write to the storage.

MQ HA deployments typically use Replicated Data Queue Manager (RDQM) or Persistent Volumes with RWO access mode.

C. API Connect → Incorrect

API Connect stores most of its configurations in databases like MongoDB but does not specifically require RWX storage for its primary operation.

It uses RWO or ReadOnlyMany (ROX) storage for its internal components.

D. Event Streams → Incorrect

Event Streams (based on Apache Kafka) uses RWO storage for high-performance message persistence.

Each Kafka broker typically writes to its own dedicated storage, meaning RWX is not required.

Explanation of Incorrect Answers:

IBM Cloud Pak for Integration Storage Requirements

CouchDB Asset Repository in CP4I

IBM MQ Multi-Instance Setup

OpenShift RWX Storage Options

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