Pass the IBM Certified Administrator - IBM Cloud Pak for Business Automation v21.0.3 C1000-150 Questions and answers with ExamsMirror

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

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/

If security pods are not scheduled, then a Cloud Pak for Business Automation Administrator should check the Resource Registry as it may not be correctly configured. The Resource Registry is the central repository for all resources used by the pods and is used to define the resources used by the pods.

References: [1] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/cpd/administer/res_registry.html  [2] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/cpd/administer/overview.html

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.

Operator log files can be retrieved from the Ansible directory. The Ansible directory is located in the home directory at ~/.ansible/logs.

References: [1] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/cpd/troubleshoot/operator_logs.html  [2] https://docs.ansible.com/ansible/latest/reference_appendices/config.html#ansible-log-dir

When logging into the product cluster console and it takes a long time or times out, one possible issue could be that the auth-idp pod is down. The auth-idp pod is responsible for authenticating users and providing them with access to the console. If this pod is down, users will not be able to log in and the console will not be accessible. This issue can be resolved by starting the auth-idp pod.

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

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

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

ILMT (IBM License Metric Tool) report uses Processor Value Unit (PVU) to determine licensing cost. PVU is a unit of measurement used to determine the licensing requirements for certain IBM software products, including IBM Business Automation Workflow. PVU is based on the number of processor cores in a physical or virtual server, and the software vendor uses this information to determine the licensing cost.

It's important to note that PVU is different from other units of measurement such as API Calls or Resource Value Unit.

IBM Cloud Pak foundational services monitoring requires Role-based access control (RBAC) to monitor APIs and data. This ensures that only authorized users have access to the data and APIs that are being monitored. It also ensures that data is only being accessed by users with the appropriate permissions. Kibana is used as the data source for the Cloud Pak foundational services monitoring. Adopter customization is only necessary to query and visualize application metrics. Red Hat OpenShift Container Platform monitoring is not required for Cloud Pak foundational services monitoring.

References: [1] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/monitoring/overview.html  [2] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/monitoring/rbac.html