Question 1

When dealing with OpenShift Container Platform (OCP) logs and log persistence, which component collects all node and container logs and stores them in a dedicated project indexes?

Accepted Answer

B

Explanation: In the OpenShift Container Platform (OCP) logging architecture, which is based on the EFK stack (Elasticsearch, Fluentd, Kibana), Fluentd acts as the log collector agent. It is deployed as a DaemonSet, meaning an instance runs on every node in the cluster. Fluentd's primary responsibility is to collect all container logs (from stdout/stderr) and node logs (from journald). After collecting the logs, it enriches them with metadata, such as the pod and namespace, and then forwards them to the configured log store, which is typically Elasticsearch. Elasticsearch then stores and indexes the data, often creating separate indices for different projects.

Question 2

What is the benefit of using the Rsyslog Sidecar?

Accepted Answer

A

Explanation: The Rsyslog sidecar pattern simplifies the integration of services with the audit logging infrastructure. The primary application container can write its audit logs to a standard output (stdout) or a file, without needing to implement the logic for secure, reliable log transmission. The sidecar container runs in the same Pod, reads these logs, and takes on the responsibility of forwarding them to the central Fluentd service over a secure channel (TLS). This decouples the application from the logging mechanism, offering an easy adoption path for audit logging and offloading the transmission burden.

Question 3

A new modification to the current Deployment has rendered it unstable. How can stability be regained?

Accepted Answer

D

Explanation: Kubernetes Deployments maintain a revision history of changes made to their Pod templates. When a new revision, introduced by a modification, proves to be unstable (e.g., causing pods to crash-loop), the standard and intended recovery mechanism is to perform a rollback. The kubectl rollout undo deployment/ command reverts the Deployment's template to a previous, stable revision, triggering a new rollout that replaces the unstable pods with pods based on the last known-good configuration, thereby restoring stability.

Question 4

Which statement is true for the Cloud Pak for Business Automation standard capabilities logging?

Accepted Answer

A

Explanation: The standard logging capability for IBM Cloud Pak for Business Automation is based on the Elasticsearch, Fluentd, and Kibana (EFK) stack, which is provided by IBM Cloud Pak foundational services. This logging service is not enabled by default. An administrator must explicitly install the logging operator and configure the service. Once configured, it collects the standard output (stdout) and standard error (stderr) logs from the containers and forwards them to a centralized, persistent data store (Elasticsearch) for aggregation and analysis.

Question 5

Container Application Software for Enterprises (CASE) is a specification that defines what?

Accepted Answer

A

Explanation: Container Application Software for Enterprises (CASE) is a specification that defines a file structure for packaging, managing, and unpacking containerized applications. A CASE file acts as a package containing all the necessary configuration and metadata for an application, including its dependencies, Helm charts, and container image references. This structure is crucial for simplifying and automating the deployment of applications, particularly in offline or air-gapped environments, by ensuring all required components are bundled together in a consistent, discoverable format.

Question 6

Which parameter is required to forward audit logging?

Accepted Answer

B

Explanation: The ENABLEAUDITLOGGINGFORWARDING parameter is a specific configuration setting used to activate the forwarding of audit logs from the IBM platform to an external Security Information and Event Management (SIEM) system. Setting this parameter to true enables the mechanism that sends generated audit records to a configured syslog endpoint. This is distinct from simply enabling the audit service itself; it specifically controls the egress of the log data.

Question 7

After scaling a Process Mining deployment, which two replica set values are updated?

Accepted Answer

A, E

Explanation: When scaling an IBM Process Mining deployment, which runs on a container orchestration platform like Red Hat OpenShift, the administrator modifies the Custom Resource (CR) to specify the target number of replicas. This action directly updates the DESIRED state in the corresponding Deployment or StatefulSet object. The platform's controller then initiates the scaling process, creating or terminating pods to match this new desired state. As these new pods start and become fully operational (passing their readiness probes), the READY count is updated to reflect the current number of available and healthy replicas.

Question 8

What are two optional components for the FileNet capability?

Accepted Answer

A, B

Explanation: The FileNet capability, architecturally known as FileNet P8 Platform, is modular. The Content Platform Engine (E) is the only mandatory core component. Other components are added to provide specific functionality. Content Search Services (A) is an optional component that enables full-text indexing and content-based searching of documents stored in the repository. Without it, searches are limited to metadata. Content Management Interoperability Services (CMIS) (B) is an optional component that provides a standardized (OASIS) web services interface, allowing third-party applications to interact with the FileNet repository in a vendor-neutral way. Both are distinct, separately deployed modules that extend the core platform.

Question 9

Prior to deploying the Cloud Pak for Business Automation operator, which two common prerequisites exist for all Cloud Pak for Business Automation capabilities (excluding Business Automation Insights)?

Accepted Answer

A, C

Explanation: Prior to deploying any IBM Cloud Pak for Business Automation capabilities, the underlying platform and cluster must be prepared. A user registry, such as an LDAP directory, is a mandatory prerequisite for the platform's Identity and Access Management (IAM) service, which handles authentication for all capabilities. Similarly, all stateful components within the Cloud Pak require persistent storage. Therefore, having pre-configured storage classes that can provision Persistent Volumes is a fundamental cluster-level prerequisite. These two elements, LDAP and Persistent Volumes, are foundational requirements for the platform itself, and thus are common prerequisites for any and all capabilities that will be deployed on it.

Question 10

Which role/persona is responsible for configuring storage for Cloud Pak for Business Automation capabilities?

Accepted Answer

A

Explanation: The Cloud Pak System Administrator is responsible for the deployment, configuration, and management of the IBM Cloud Pak for Business Automation instance. A key part of this responsibility is creating and customizing the Custom Resource (CR) file. This file specifies the configuration details for the deployment, including which pre-existing storage classes to use for the various capabilities' Persistent Volume Claims (PVCs), storage sizes, and access modes. While the Cluster Administrator makes storage available at the cluster level, the Cloud Pak System Administrator configures its specific use for the Cloud Pak's components.

Question 11

Which step is required to enable a trace specification for Business Automation Workflow?

Accepted Answer

C

Explanation: To enable a custom trace specification in a containerized IBM Business Automation Workflow (BAW) environment, the administrator must first define the trace settings in a logging.xml file. This file is then packaged into a Kubernetes ConfigMap. The ConfigMap acts as a vehicle to inject this custom configuration into the BAW pods. Finally, the Custom Resource (CR) is updated to reference this ConfigMap, triggering the operator to apply the changes. Creating the ConfigMap is the pivotal step that makes the trace configuration a manageable and deployable resource within the Kubernetes cluster.

Question 12

During a Cloud Pak for Business Automation installation, which component helps install, update, and
manage the lifecycle of all operators and services that are deployed in OpenShift Container Platform
clusters?

Accepted Answer

B

Explanation: The Operator Lifecycle Manager (OLM) is a core component of OpenShift Container Platform that is responsible for managing the entire lifecycle of Kubernetes Operators. During the installation of IBM Cloud Pak for Business Automation, OLM automates the process of installing, upgrading, and managing the dependencies of the CP4BA operator and all its related services. It uses catalog sources to discover available operators and then handles their deployment and ongoing management, ensuring the cluster's services remain consistent and stable.

Question 13

Which command is used to verify that all the pods are running after Operators are deployed?

Accepted Answer

D

Explanation: The oc get pods command is the standard and most direct method used in OpenShift to list all pod resources within a specified namespace. Its output provides a concise, tabular view of each pod's name, ready state, overall status (e.g., Running, Pending, Completed), number of restarts, and age. This makes it the ideal command to quickly verify that all pods deployed by an Operator are in the expected 'Running' state after an installation or update.

Question 14

To manually scale up the Process Mining deployment in the IBM Cloud Pak for Business Automation, which parameter section needs to be updated in the custom resource YAML file?

Accepted Answer

D

Explanation: To manually scale a Process Mining deployment, an administrator must modify the custom resource (CR) YAML file. The replicas parameter within the specification (spec) of a particular component (e.g., engine, UI) dictates the number of running pods for that service. Increasing the integer value of the replicas parameter and applying the change instructs the IBM Cloud Pak for Business Automation operator to provision additional pods, thus scaling up the service to handle a higher load.

Question 15

Which component is responsible for removing sensitive data in Business Automation Insights?

Accepted Answer

D

Explanation: IBM Business Automation Insights (BAI) uses a configurable mechanism to protect sensitive personal data. This is achieved by defining anonymization or obfuscation rules in a JSON configuration file. These rules are applied by the Apache Flink processing jobs before the data is stored in Elasticsearch. The rules specify which data fields to anonymize and the method to use (e.g., masking, hashing). This process effectively removes the sensitive nature of the data from the stored events, ensuring compliance with privacy regulations like GDPR.

Free IBM C1000-150 Actual Exam Questions