Free Practice Questions for IBM C1000-130 Exam

In IBM Cloud Pak for Integration (CP4I) v2021.2, when new IBM MQ (Message Queue) containers are deployed, sensitive data such as passwords, credentials, and encryption keys must be securely injected into the container environment.

The correct Kubernetes object for storing and injecting sensitive data is a Secret.

Kubernetes Secrets securely store sensitive data

Secrets allow IBM MQ containers to retrieve authentication credentials (e.g., admin passwords, TLS certificates, and API keys) without exposing them in environment variables or config maps.

Unlike ConfigMaps, Secrets are encrypted and access-controlled, ensuring security compliance.

Used by IBM MQ Operator

When deploying IBM MQ in OpenShift/Kubernetes, the MQ operator references Secrets to inject necessary credentials into MQ containers.

Example:

Why is "Secret" the correct answer?apiVersion: v1

kind: Secret

metadata:

name: mq-secret

type: Opaque

data:

mq-password: bXlxYXNzd29yZA==

The MQ container can then access this mq-password securely.

Prevents hardcoding sensitive data

Instead of storing passwords directly in deployment files, using Secrets enhances security and compliance with enterprise security standards.

Why are the other options incorrect?❌ A. Replicator

The Replicator is responsible for synchronizing and replicating messages across MQ queues but does not store sensitive credentials.

❌ B. MQRegistry

The MQRegistry is used for tracking queue manager details but does not manage sensitive data injection.

It mainly helps with queue manager registration and configuration.

❌ C. DeploymentConfig

A DeploymentConfig in OpenShift defines how pods should be deployed but does not handle sensitive data injection.

Instead, DeploymentConfig can reference a Secret, but it does not store sensitive information itself.

IBM MQ Security - Kubernetes Secrets

IBM Docs – Securely Managing MQ in Kubernetes

IBM Cloud Pak for Integration Knowledge Center

Covers how Secrets are used in MQ container deployments.

Red Hat OpenShift Documentation – Kubernetes Secrets

Secrets in Kubernetes

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

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

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.

Analysis of Key Fields:

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 CP4I Logging and Monitoring Documentation

Red Hat OpenShift Logging Documentation

Elasticsearch Redundancy Policies in OpenShift Logging

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

In IBM Cloud Pak for Integration (CP4I) v2021.2, the IBM License Service collects and retains license usage data for a default period of 90 days. This data is crucial for auditing and compliance, ensuring that software usage aligns with licensing agreements.

The IBM License Service continuously collects and stores licensing data.

By default, it retains data for 90 days before older data is automatically removed.

Users can query and retrieve usage reports from this 90-day period.

The License Service supports regulatory compliance by ensuring transparent tracking of software usage.

B. The full period from the deployment – Incorrect. The License Service does not retain data indefinitely; it follows a rolling 90-day retention policy.

C. 30 days – Incorrect. The default retention period is longer than 30 days.

D. 60 days – Incorrect. The default is 90 days, not 60.

IBM License Service Documentation

IBM Cloud Pak for Integration v2021.2 – Licensing Guide

IBM Support – License Service Data Retention Policy

Key Details About the IBM License Service Data Retention:Why Not the Other Options?IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References