IBM C1000-150 IBM Cloud Pak for Business Automation v21.0.3 Administration Exam Practice Test

The Cloud Pak System Administrator is responsible for configuring storage for Cloud Pak for Business Automation capabilities.

References: [1] https://www.ibm.com/support/knowledgecenter/SSFTN5_20.2/com.ibm.cic.customize.doc/topics/r_storage_config_cloudpak.html  [2] https://www.ibm.com/support/knowledgecenter/SSFTN5_20.2/com.ibm.cic.customize.doc/topics/r_cloudpak_overview_architecture.html

The parameters for accessing the images in an OpenShift Container Platform environment are set using the oc set command. This command allows you to set image pull secrets and other image-related parameters.

References: [1] https://docs.openshift.com/container-platform/4.4/openshift_images/image-pull-secrets.html  [2] https://docs.openshift.com/container-platform/4.4/cli_reference/openshift_cli/oc-set.html

In an OpenShift Container Platform environment, the parameters for accessing images are set using the "oc set" command. The "oc set" command allows an administrator to configure various aspects of a deployment, such as environment variables, resource limits, and image pull secrets. These parameters can be set for a specific deployment, service, pod, or other resource in the OpenShift cluster.

The most suitable probe in this case would be a liveness probe. This type of probe is used to detect if an application is running correctly and is able to respond to requests. It is usually used in conjunction with a readiness probe to ensure that the application is both healthy and ready to serve requests.

To enable a trace specification for Business Automation Workflow, you must create a ConfigMap. This ConfigMap will contain the trace specification that you wish to enable.

References: [1] https://www.ibm.com/support/knowledgecenter/SSFTN5_9.7.1/com.ibm.wbpm.inst.doc/topics/t_trace_spec.html  [2] https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/

https://www.ibm.com/docs/en/cpfs?topic=operator-architecture-audit-logging-version-370

Rsyslog is an open-source software utility for forwarding log messages in an IP network. It can act as a centralized log server and can also be used as a sidecar in a Kubernetes environment. The Rsyslog sidecar can be used to provide easier adoption of audit logging by shifting the burden of transmitting log messages to the sidecar. This allows for a more streamlined process for implementing audit logging within a Kubernetes environment.

When performing an air-gapped upgrade of Cloud Pak for Business Automation, the images used for the upgrade reside in a local registry. An air-gapped environment is one in which there is no external network access, so the images cannot be pulled from a remote registry such as IBM registry, RedHat quay.io registry, or Docker Hub. Instead, the images must be pre-pulled and stored in a local registry that is accessible to the OpenShift cluster.

The two foundation pattern components that are always deployed with any of the Cloud Pak for Business Automation capabilities are Business Automation Navigator (BAN) and Resource Registry (RR). BAN provides an entry point for users to access the Business Automation capabilities, while RR is the repository for the resources used in the deployment process. The other options are not related to this process.

References: [1] https://www.ibm.com/support/knowledgecenter/SSFTN5_9.7.1/com.ibm.wbpm.inst.doc/topics/t_patterns_overview.html  [2] https://www.ibm.com/support/knowledgecenter/SSFTN5_9.7.1/com.ibm.wbpm.inst.doc/topics/t_patterns_ban.html  [3] https://www.ibm.com/support/knowledgecenter/SSFTN5_9.7.1/com.ibm.wbpm.inst.doc/topics/t_patterns

Business Automation Navigator (BAN) is a web-based application that provides a central location for managing and monitoring the automation capabilities. Resource Registry (RR) is a centralized metadata repository that holds information about the automation capabilities. Together, BAN and RR provide the foundation for managing and monitoring the automation capabilities, and for storing metadata about the automation capabilities.

If it is desired to use a root CA signer certificate that is signed by a recognized certificate authority, the rootcacertificate should be supplied as part of the custom resource prior to deployment. This is necessary in order for the root CA signer certificate to be validated.

References: [1] https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-certificates/#running-an-https-server  [2] https://kubernetes.io/docs/concepts/cluster-administration/certificates/

When using the product Certificate manager service, the default setting of refreshing certificates is disabled. Pods that use the refreshed certificate do not need to be manually restarted, as certificate refresh will be automatically enabled when the certificate expires.