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

In IBM Cloud Pak for Integration (CP4I) v2021.2, licensing is based on Virtual Processor Cores (VPCs), and it includes entitlement for OpenShift usage. However, OpenShift master nodes (control plane nodes) do not consume license entitlement, because:

OpenShift licensing only applies to worker nodes.

The master nodes (control plane nodes) manage cluster operations and scheduling, but they do not run user workloads.

IBM’s Cloud Pak licensing model considers only the worker nodes for licensing purposes.

Master nodes are essential infrastructure and are excluded from entitlement calculations.

IBM and Red Hat do not charge for OpenShift master nodes in Cloud Pak deployments.

A. CP4I licenses include entitlement for the entire OpenShift cluster that they run on, and the administrator can count against the master nodes. → ❌ Incorrect

CP4I licenses do cover OpenShift, but only for worker nodes where workloads are deployed.

Master nodes are excluded from licensing calculations.

C. The administrator will need to purchase additional OpenShift licenses to cover the master nodes. → ❌ Incorrect

No additional OpenShift licenses are required for master nodes.

OpenShift licensing only applies to worker nodes that run applications.

D. CP4I licenses include entitlement for 3 cores of OpenShift per core of CP4I. → ❌ Incorrect

The standard IBM Cloud Pak licensing model provides 1 VPC of OpenShift for 1 VPC of CP4I, not a 3:1 ratio.

Additionally, this applies only to worker nodes, not master nodes.

Explanation of Incorrect Answers:

IBM Cloud Pak Licensing Guide

IBM Cloud Pak for Integration Licensing Details

Red Hat OpenShift Licensing Guide

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

IBM Cloud Pak for Integration (CP4I) v2021.2 is designed to run on containerized environments that support Red Hat OpenShift, which can be deployed on various public clouds and on-premises environments. The two correct options that support CP4I deployments are:

Amazon Web Services (AWS) (Option B) ✅

AWS supports IBM Cloud Pak for Integration via Red Hat OpenShift on AWS (ROSA) or self-managed OpenShift clusters running on AWS EC2 instances.

CP4I components such as API Connect, App Connect, MQ, and Event Streams can be deployed on OpenShift running on AWS.

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: