C1000-150 IBM Cloud Pak for Business Automation v21.0.3 Administration Questions and Answers

The Cloud Pak Foundation services monitoring stack includes Kibana, which is an open-source data visualization and exploration tool. It allows you to search, view, and interact with data stored in Elasticsearch indices. Kibana provides a web interface that enables you to create and share dynamic dashboards, visualizations, and search templates.

It's important to note that other tools such as Elasticsearch, Alertmanager, and Logstash are also part of the Cloud Pak Foundation services monitoring stack, but they have different functions.

When deploying the Cloud Pak for Business Automation, the starter deployment requires one capability to be installed independently:

Operational Decision Manager (ODM) and Automation Decision Services (ADS): These capabilities provide a set of tools for creating and managing business rules, decision services, and analytics. They are typically used to automate decision-making processes within an organization.

https://www.ibm.com/support/knowledgecenter/en/SSYHZ8_20.0.x/com.ibm.dba.baw.install/topics/install_overview.html

In preparing the IBM Business Automation Studio and Application Engine environments for recovery, the sharedconfiguration. scrunasuser in the CR definition must have the same UID in common between the primary and secondary environments. This ensures that the same user account is used in both primary and secondary environments for disaster recovery.

References: [1] https://www.ibm.com/support/knowledgecenter/SSFTN5_9.7.1/com.ibm.wbpm.inst.doc/topics/t_ha_install_intro.html  [2] https://www.ibm.com/support/knowledgecenter/SSFTN5_9.7.1/com.ibm.wbpm.inst.doc/topics/t_ha_install_configure_cr.html

It's also important that the primary and secondary environments have the same OpenShift administrator account and the same router hostname, but it's not necessary that they have identical LDAP configurations.

If a new modification to a Deployment has rendered it unstable, then the best way to regain stability is to rollback to an earlier Deployment. Rolling back to a previous Deployment will restore the system to its previous configuration, which should restore stability. The other options are not related to this process.

References: [1] https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/  [2] https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#rollback

The rpa-owner permission must be granted in order for the option to appear in the Platform UI navigation menu. If you would like to grant the permission, please follow these steps: 1) Log into the Robotic Process Automation (RPA) server 2) Navigate to the Settings tab 3) Select the Security tab 4) Select the Roles & Permissions tab 5) Select the rpa-owner permission 6) Click Save.

The best data to check for installation and upgrade problems is Pod status. Pods are the smallest deployable units in a Kubernetes cluster and contain the necessary components to run an application. Examining the Pod status can help identify any issues that may be present with the installation or upgrade process. The other options are not related to this process.

References: [1] https://kubernetes.io/docs/concepts/workloads/pods/  [2] https://kubernetes.io/docs/tasks/debug-application-cluster/debug-cluster-upgrade/