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

When installing a new instance of IBM Cloud Pak for Integration (CP4I) Operations Dashboard, several prerequisites must be met. The correct answers are B and D based on IBM Cloud Pak for Integration v2021.2 requirements.

B. A pull secret from IBM Entitled Registry must exist in the namespace containing an entitlement key.

The IBM Entitled Registry hosts the necessary container images required for CP4I components, including Operations Dashboard.

Before installation, you must create a pull secret in the namespace where CP4I is installed. This secret must include your IBM entitlement key to authenticate and pull images.

Command to create the pull secret:

Correct Answers:oc create secret docker-registry ibm-entitlement-key \

--docker-server=cp.icr.io \

--docker-username=cp \

--docker-password= \

--namespace=

IBM Reference: IBM Entitled Registry Setup

D. The vm.max_map_count sysctl setting on worker nodes must be higher than the operating system default.

The Operations Dashboard relies on Elasticsearch, which requires an increased vm.max_map_count setting for better performance and stability.

The default Linux setting (65530) is too low. It needs to be at least 262144 to avoid indexing failures.

To update this setting permanently, run the following command on worker nodes:

sudo sysctl -w vm.max_map_count=262144

IBM Reference: Elasticsearch System Requirements

A. For shared data, a storage class that provides ReadWriteOnce (RWO) access mode of at least 100 MB is required. (Incorrect)

While persistent storage is required, the Operations Dashboard primarily uses Elasticsearch, which typically requires ReadWriteOnce (RWO) or ReadWriteMany (RWX) block storage. However, the 100 MB storage requirement is incorrect, as Elasticsearch generally requires gigabytes of storage, not just 100 MB.

IBM Recommendation: Typically, Elasticsearch requires at least 10 GB of persistent storage for logs and indexing.

C. If the OpenShift Container Platform Ingress Controller pod runs on the host network, the default namespace must be labeled with network.openshift.io/controller-group: ingress to allow traffic to the Operations Dashboard. (Incorrect)

While OpenShift’s Ingress Controller must be configured correctly, this specific label requirement applies to some specific OpenShift configurations but is not a mandatory prerequisite for Operations Dashboard installation.

Instead, route-based access and appropriate network policies are required to allow ingress traffic.

E. For storing tracing data, a block storage class that provides ReadWriteMany (RWX) access mode and 10 IOPS of at least 10 GB is required. (Incorrect)

Tracing data storage does require persistent storage, but block storage does not support RWX mode in most environments.

Instead, file-based storage with RWX access mode (e.g., NFS) is typically used for OpenShift deployments needing shared storage.

Explanation of Incorrect Options:

IBM Cloud Pak for Integration Operations Dashboard Installation Guide

Setting Up IBM Entitled Registry Pull Secret

Elasticsearch System Configuration - vm.max_map_count

OpenShift Storage Documentation

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

Final Answer:✅ B. A pull secret from IBM Entitled Registry must exist in the namespace containing an entitlement key.✅ D. The vm.max_map_count sysctl setting on worker nodes must be higher than the operating system default.

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 IBM Cloud Pak for Integration (CP4I), IBM MQ Native High Availability (NativeHA) is a feature that enables automated failover and redundancy by maintaining multiple replicas of an MQ queue manager.

When using NativeHA, licensing in CP4I is calculated based on the total number of VPCs (Virtual Processor Cores) consumed by all MQ instances, including both active and standby replicas.

IBM MQ NativeHA uses a multi-replica setup, meaning there are multiple queue manager instances running simultaneously for redundancy.

Licensing in CP4I is based on the total CPU consumption of all running MQ replicas, not just the active instance.

Therefore, the administrator must ensure that all HA replicas are accounted for in their license entitlement.

Why Option B is Correct:

A. No licenses, because only RDQM is supported on CP4I. (Incorrect)

IBM MQ NativeHA is fully supported on CP4I alongside RDQM (Replicated Data Queue Manager). NativeHA is actually preferred over RDQM in containerized OpenShift environments.

C. A different license from the standard CP4I license must be purchased from IBM to use the NativeHA feature. (Incorrect)

No separate license is required for NativeHA – it is covered under the CP4I licensing model.

D. The administrator can use their pool of CP4I licenses. (Incorrect)

Partially correct but incomplete – while the administrator can use their CP4I licenses, they must ensure that all HA replicas are included in the license calculation, not just the active instance.

Analysis of the Incorrect Options:

IBM MQ Native High Availability Licensing

IBM Cloud Pak for Integration Licensing Guide

IBM MQ on CP4I - Capacity Planning and Licensing

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