IBM C1000-130 Dumps - Pass IBM Cloud Pak for Integration V2021.2 Administration Exam in 2026

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.

Why Option B is Correct:

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.

Analysis of the Incorrect Options:

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.

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

IBM MQ Native High Availability Licensing

IBM Cloud Pak for Integration Licensing Guide

IBM MQ on CP4I - Capacity Planning and Licensing

The given YAML configuration is for ClusterLogging in an OpenShift environment, which is used for centralized logging. The key part of the specification that determines the behavior of Elasticsearch is:

logStore:

type: 'elasticsearch'

elasticsearch:

nodeCount: 1

storage: {}

redundancyPolicy: ZeroRedundancy

Analysis of Key Fields:

nodeCount: 1

This means the Elasticsearch cluster will consist of only one node (single-node deployment).

storage: {}

The empty storage field implies no persistent storage is configured.

This means that if the pod is deleted or restarted, all stored logs will be lost.

redundancyPolicy: ZeroRedundancy

ZeroRedundancy means there is no data replication, making the system vulnerable to data loss if the pod crashes.

In contrast, a redundancy policy like MultiRedundancy ensures high availability by replicating data across multiple nodes, but that is not the case here.

Evaluating Answer Choices:

Option

Explanation

Correct?

A . A single node ElasticSearch cluster with default persistent storage.

Incorrect, because storage: {} means no persistent storage is configured.

B . A single infrastructure node with persisted ElasticSearch.

Incorrect, as this is not configuring an infrastructure node, and storage is not persistent.

C . A single node ElasticSearch cluster which auto scales when redundancyPolicy is set to MultiRedundancy.

Incorrect, because setting MultiRedundancy does not automatically enable auto-scaling. Scaling needs manual intervention or Horizontal Pod Autoscaler (HPA).

D . A single node ElasticSearch cluster with no persistent storage.

Correct, because nodeCount: 1 creates a single node, and storage: {} ensures no persistent storage.

Final Answer:

D. A single node ElasticSearch cluster with no persistent storage.

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

IBM CP4I Logging and Monitoring Documentation

Red Hat OpenShift Logging Documentation

Elasticsearch Redundancy Policies in OpenShift Logging

OpenShift Pipelines are based on Tekton, an open-source framework for building Continuous Integration/Continuous Deployment (CI/CD) pipelines natively in Kubernetes.

Tekton provides Kubernetes-native CI/CD functionality by defining pipeline resources as custom resources (CRDs) in OpenShift. This allows for scalable, cloud-native automation of software delivery.

Why Tekton is Used in OpenShift Pipelines?

Kubernetes-Native: Unlike Jenkins, which requires external servers or agents, Tekton runs natively in OpenShift/Kubernetes.

Serverless & Declarative: Pipelines are defined using YAML configurations, and execution is event-driven.

Reusable & Extensible: Developers can define Tasks, Pipelines, and Workspaces to create modular workflows.

Integration with GitOps: OpenShift Pipelines support Argo CD for GitOps-based deployment strategies.

Example of a Tekton Pipeline Definition in OpenShift:

apiVersion: tekton.dev/v1beta1

kind: Pipeline

metadata:

name: example-pipeline

spec:

tasks:

- name: echo-hello

taskSpec:

steps:

- name: echo

image: ubuntu

script: |

#!/bin/sh

echo 'Hello, OpenShift Pipelines!'

Explanation of Incorrect Answers:

A . Travis Incorrect

Travis CI is a cloud-based CI/CD service primarily used for GitHub projects, but it is not used in OpenShift Pipelines.

B . Jenkins Incorrect

OpenShift previously supported Jenkins-based CI/CD, but OpenShift Pipelines (Tekton) is now the recommended Kubernetes-native alternative.

Jenkins requires additional agents and servers, whereas Tekton runs serverless in OpenShift.

D . Argo CD Incorrect

Argo CD is used for GitOps-based deployments, but it is not the underlying technology of OpenShift Pipelines.

Tekton and Argo CD can work together, but Argo CD alone does not handle CI/CD pipelines.

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

IBM Cloud Pak for Integration CI/CD Pipelines

Red Hat OpenShift Pipelines (Tekton)

Tekton Pipelines Documentation

In IBM Cloud Pak for Integration (CP4I) v2021.2, which runs on Red Hat OpenShift, cluster logging can be forwarded to external third-party systems, with Splunk being one of the officially supported destinations.

OpenShift Log Forwarding Features:

OpenShift Cluster Logging Operator enables log forwarding.

Supports forwarding logs to various external logging solutions, including Splunk.

Uses the Fluentd log collector to send logs to Splunk's HTTP Event Collector (HEC) endpoint.

Provides centralized log management, analysis, and visualization.

Why Not the Other Options?

B . Kafka Broker -- OpenShift does support sending logs to Kafka, but Kafka is a message broker, not a full-fledged logging system like Splunk.

C . Apache Lucene -- Lucene is a search engine library, not a log management system.

D . Apache Solr -- Solr is based on Lucene and is used for search indexing, not log forwarding.

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

OpenShift Log Forwarding to Splunk

IBM Cloud Pak for Integration -- Logging and Monitoring

Red Hat OpenShift Logging Documentation

When deploying IBM DataPower Gateway as part of IBM Cloud Pak for Integration (CP4I) v2021.2, administrators can enable a selected list of add-on modules based on their requirements. This allows customization and optimization of the deployment by enabling only the necessary features.

Why Option B is Correct:

IBM DataPower Gateway deployed in Cloud Pak for Integration is a containerized version that supports modular configurations.

Administrators can enable or disable add-on modules to optimize resource utilization and security.

Some of these modules include:

API Gateway

XML Processing

MQ Connectivity

Security Policies

This flexibility helps in reducing overhead and ensuring that only the necessary capabilities are deployed.

Explanation of Incorrect Answers:

A . Only the datapower-cp4i image can be deployed. Incorrect

While datapower-cp4i is the primary image used within Cloud Pak for Integration, other variations of DataPower can also be deployed outside CP4I (e.g., standalone DataPower Gateway).

C . This image deployment brings all the functionality of DataPower as it runs with root permissions. Incorrect

The DataPower container runs as a non-root user for security reasons.

Not all functionalities available in the bare-metal or VM-based DataPower appliance are enabled by default in the containerized version.

D . The datapower-cp4i image will be downloaded from the dockerhub enterprise account of IBM. Incorrect

IBM does not use DockerHub for distributing CP4I container images.

Instead, DataPower images are pulled from the IBM Entitled Registry (cp.icr.io), which requires an IBM Entitlement Key for access.

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

IBM Cloud Pak for Integration - Deploying DataPower Gateway

IBM DataPower Gateway Container Deployment Guide

IBM Entitled Registry - Pulling CP4I Images