Pass the IBM Certified Administrator - Cloud Pak for Integration V2021.2 C1000-130 Questions and answers with ValidTests

Single Sign-On (SSO) is an authentication mechanism that allows users to log in once and gain access to multiple applications without re-entering credentials. In IBM Cloud Pak for Integration (CP4I), Enterprise LDAP and OpenShift authentication both support SSO.

Enterprise LDAP (B) – ✅ Supports SSO

Lightweight Directory Access Protocol (LDAP) is commonly used in enterprises for centralized authentication.

CP4I can integrate with Enterprise LDAP, allowing users to authenticate once and access multiple cloud services without needing separate logins.

OpenShift Authentication (E) – ✅ Supports SSO

OpenShift provides OAuth-based authentication, enabling SSO across multiple OpenShift-integrated services.

CP4I uses OpenShift’s built-in identity provider to allow seamless user authentication across different Cloud Pak components.

A. 2FA (Incorrect):

Two-Factor Authentication (2FA) enhances security by requiring an additional verification step but does not inherently support SSO.

C. Plain Text over HTTPS (Incorrect):

Plain text authentication is insecure and does not support SSO.

D. Enterprise SSH (Incorrect):

SSH authentication is used for remote access to servers but is not related to SSO.

Analysis of the Incorrect Options:

IBM Cloud Pak for Integration Authentication & SSO Guide

Red Hat OpenShift Authentication and Identity Providers

IBM Cloud Pak - Integrating with Enterprise LDAP

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, Identity and Access Management (IAM) is part of Foundational Services, which provides authentication and authorization across different modules within CP4I.

When configuring IAM for single sign-on (SSO), the administrator must have administrator access to the IAM service. This is essential for:

Integrating external identity providers (IdPs) such as LDAP, SAML, or OIDC.

Managing user roles and access control policies across the Cloud Pak environment.

Configuring SSO settings for seamless authentication across all IBM Cloud Pak services.

IAM service administrators have full control over authentication and SSO settings.

They can configure and integrate identity providers for authentication.

This level of access is required to modify IAM settings in Cloud Pak for Integration.

Why Answer D (Access to IAM service as administrator) is Correct?

A. Access to the OpenShift Container Platform console as kubeadmin. → Incorrect

While kubeadmin is a cluster-wide OpenShift administrator, this role does not grant IAM administrative privileges in Cloud Pak Foundational Services.

IAM settings are managed within IBM Cloud Pak, not solely through OpenShift.

B. Access to IBM Cloud Pak for Integration as kubeadmin. → Incorrect

kubeadmin can manage OpenShift resources, but IAM requires specific access to the IAM service within Cloud Pak.

IAM administrators are responsible for configuring authentication, SSO, and identity providers.

C. Access to OpenShift cluster as root. → Incorrect

Root access is not relevant here because OpenShift does not use root users for administration.

IAM configurations are done within Cloud Pak, not at the OpenShift OS level.

Explanation of Incorrect Answers:

IBM Cloud Pak Foundational Services - IAM Configuration

Configuring Single Sign-On (SSO) in IBM Cloud Pak

IBM Cloud Pak for Integration Security Overview

OpenShift Authentication and Identity Management

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