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

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.

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

Why Option B is Correct:This flexibility helps in reducing overhead and ensuring that only the necessary capabilities are deployed.

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.

Explanation of Incorrect Answers:

IBM Cloud Pak for Integration - Deploying DataPower Gateway

IBM DataPower Gateway Container Deployment Guide

IBM Entitled Registry - Pulling CP4I Images

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

In IBM Aspera High-Speed Transfer Server (HSTS), UDP ports are crucial for enabling high-speed data transfers. When multiple instances of Aspera HSTS exist in a cluster, each instance must be assigned a unique UDP port to avoid conflicts and ensure proper traffic routing.

Aspera HSTS relies on UDP for high-speed file transfers (as opposed to TCP, which is typically used for control and session management).

If multiple HSTS instances share the same UDP port, packet collisions and routing issues can occur.

Ensuring unique UDP ports across instances allows for proper load balancing and optimal performance.

B. UDP and TCP ports have to be the same.

Incorrect, because UDP and TCP serve different purposes in Aspera HSTS.

TCP is used for session initialization and control, while UDP is used for actual data transfer.

C. Each TCP port must be unique.

Incorrect, because TCP ports do not necessarily need to be unique across multiple instances, depending on the deployment.

TCP ports can be shared if proper load balancing and routing are configured.

D. UDP ports must be the same.

Incorrect, because using the same UDP port for multiple instances causes conflicts, leading to failed transfers or degraded performance.

Key Considerations for Aspera HSTS in a Cluster:Why Other Options Are Incorrect:IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References:

IBM Aspera HSTS Configuration Guide

IBM Cloud Pak for Integration - Aspera Setup

IBM Aspera High-Speed Transfer Overview

In IBM Cloud Pak for Integration (CP4I) v2021.2, App Connect Enterprise (ACE) Dashboard requires persistent storage to maintain configurations, logs, and runtime data. The supported storage type for the ACE Dashboard instance is file storage because:

It supports ReadWriteMany (RWX) access mode, allowing multiple pods to access shared data.

It ensures data persistence across restarts and upgrades, which is essential for managing ACE integrations.

It is compatible with NFS, IBM Spectrum Scale, and OpenShift Container Storage (OCS), all of which provide file system-based storage.

A. Ephemeral storage – Incorrect

Ephemeral storage is temporary and data is lost when the pod restarts or gets rescheduled.

ACE Dashboard needs persistent storage to retain configuration and logs.

B. Flash storage – Incorrect

Flash storage refers to SSD-based storage and is not specifically required for the ACE Dashboard.

While flash storage can be used for better performance, ACE requires file-based persistence, which is different from flash storage.

D. Raw block storage – Incorrect

Block storage is low-level storage that is used for databases and applications requiring high-performance IOPS.

ACE Dashboard needs a shared file system, which block storage does not provide.

Why the other options are incorrect:

IBM App Connect Enterprise (ACE) Storage Requirements

IBM Cloud Pak for Integration Persistent Storage Guide

OpenShift Persistent Volume Types

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

In IBM Cloud Pak for Integration (CP4I) v2021.2, Foundational Services provide authentication and access control mechanisms, including Single Sign-On (SSO) integration. The two supported authentication types for SSO are:

OpenShift Authentication

IBM Cloud Pak for Integration leverages OpenShift authentication to integrate with existing identity providers.

OpenShift authentication supports OAuth-based authentication, allowing users to sign in using an OpenShift identity provider, such as LDAP, OIDC, or SAML.

This method enables seamless user access without requiring additional login credentials.

Enterprise SAML (Security Assertion Markup Language)

SAML authentication allows integration with enterprise identity providers (IdPs) such as IBM Security Verify, Okta, Microsoft Active Directory Federation Services (ADFS), and other SAML 2.0-compatible IdPs.

It provides federated identity management for SSO across enterprise applications, ensuring secure access to Cloud Pak services.

A. Basic Authentication – Incorrect

Basic authentication (username and password) is not used for Single Sign-On (SSO). SSO mechanisms require identity federation through OpenID Connect (OIDC) or SAML.

C. PublicKey – Incorrect

PublicKey authentication (such as SSH key-based authentication) is used for system-level access, not for SSO in Foundational Services.

E. Local User Registry – Incorrect

While local user registries can store credentials, they do not provide SSO capabilities. SSO requires federated identity providers like OpenShift authentication or SAML-based IdPs.

Why the other options are incorrect:

IBM Cloud Pak Foundational Services Authentication Guide

OpenShift Authentication and Identity Providers

IBM Cloud Pak for Integration SSO Configuration

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

In IBM Cloud Pak for Integration (CP4I) v2021.2, OpenShift Logging utilizes Elasticsearch as its log storage backend. The default configuration of the OpenShift Logging stack is optimized for short-term storage and is designed to retain logs for approximately 7 days before they are automatically purged.

Performance Optimization: The OpenShift Logging Elasticsearch instance is designed for short-term log retention to balance storage efficiency and performance.

Default Curator Configuration: OpenShift Logging uses Elasticsearch Curator to manage the log retention policy, and by default, it is set to delete logs older than 7 days.

Designed for Operational Logs: The default OpenShift Logging stack is intended for short-term troubleshooting and monitoring, not long-term log archival.

Why is the retention period 7 days?If longer retention is required, organizations can:

Configure a different retention period by modifying the Elasticsearch Curator settings.

Forward logs to an external log storage system like Splunk, IBM Cloud Object Storage, or another long-term logging solution.

A. 1 day – Too short; OpenShift Logging does not delete logs on a daily basis by default.

B. 30 days – The default retention period is 7 days, not 30. A 30-day retention period would require manual configuration changes.

D. 6 months – OpenShift Logging is not optimized for such long-term storage. Long-term log retention should be managed using external storage solutions.

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

IBM Cloud Pak for Integration Logging and Monitoring

Red Hat OpenShift Logging Documentation

Configuring OpenShift Logging Retention Policy

OpenShift Pipelines, which are based on Tekton, use various components to define and execute CI/CD workflows. The fundamental building block for creating a Pipeline in OpenShift Pipelines is a Task.

Task (✅ Correct Answer)

A Task is the basic unit of work in Tekton.

Each Task defines a set of steps (commands) that are executed in containers.

Multiple Tasks are combined into a Pipeline to form a CI/CD workflow.

Pipeline (uses multiple Tasks)

A Pipeline is a collection of Tasks that define the entire CI/CD workflow.

Each Task in the Pipeline runs in sequence or in parallel as specified.

Key Tekton Components:

Why the Other Options Are Incorrect?Option

Explanation

Correct?

A. TaskRun

❌ Incorrect – A TaskRun is an execution instance of a Task, but it does not define the Pipeline itself.

❌

C. TPipe

❌ Incorrect – No such Tekton component called TPipe exists.

❌

D. Pipe

❌ Incorrect – The correct term is Pipeline, not "Pipe". OpenShift Pipelines do not use this term.

❌

Final Answer:✅ B. Task

OpenShift Pipelines (Tekton) Documentation

Tekton Documentation – Understanding Tasks

IBM Cloud Pak for Integration – CI/CD with OpenShift Pipelines

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

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 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.

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.

OpenShift Log Forwarding to Splunk

IBM Cloud Pak for Integration – Logging and Monitoring

Red Hat OpenShift Logging Documentation

OpenShift Log Forwarding Features:Why Not the Other Options?IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References

Within IBM Cloud Pak for Integration (CP4I) v2021.2, IBM MQ is a key messaging component that ensures reliable, secure, and auditable message delivery between applications and services. It is designed to facilitate enterprise messaging by guaranteeing message delivery, supporting transactional integrity, and providing end-to-end security features.

IBM MQ within CP4I provides the following capabilities:

Secure Messaging – Messages are encrypted in transit and at rest, ensuring that sensitive data is protected.

Auditable Transactions – IBM MQ logs all transactions, allowing for traceability, compliance, and recovery in the event of failures.

High Availability & Scalability – Can be deployed in containerized environments using OpenShift and Kubernetes, supporting both on-premises and cloud-based workloads.

Integration Across Multiple Environments – Works across different operating systems, cloud providers, and hybrid infrastructures.

Option A (Works with a limited range of computing platforms) – Incorrect: IBM MQ is platform-agnostic and supports multiple operating systems (Windows, Linux, z/OS) and cloud environments (AWS, Azure, Google Cloud, IBM Cloud).

Option B (A versatile messaging integration from mainframe to cluster) – Incorrect: While IBM MQ does support messaging from mainframes to distributed environments, this option does not fully highlight its primary function of secure and auditable messaging.

Option C (Cannot be deployed across a range of different environments) – Incorrect: IBM MQ is highly flexible and can be deployed on-premises, in hybrid cloud, or in fully managed cloud services like IBM MQ on Cloud.

IBM MQ Overview

IBM Cloud Pak for Integration Documentation

IBM MQ Security and Compliance Features

IBM MQ Deployment Options

Why the other options are incorrect:IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References: