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

In Business Automation Insights, the component responsible for removing sensitive data is the anonymization rules. These rules are used to mask or remove sensitive data from the logs before they are indexed and stored in the Business Automation Insights data lake. The anonymization rules can be defined based on the data type and the data masking or removal method. The anonymization rules are typically used to mask or remove personal data, such as names, addresses, and other identifying information.

https://www.ibm.com/support/knowledgecenter/en/SSYHZ8_20.0.x/com.ibm.dba.bai/topics/bai_admin_security_anonymization.html

https://www.ibm.com/support/knowledgecenter/en/SSYHZ8_20.0.x/com.ibm.dba.bai/topics/bai_admin_security_overview.html

https://www.ibm.com/support/knowledgecenter/en/SSYHZ8_20.0.x/com.ibm.dba.bai/topics/bai_admin_security_anonymization_overview.html

Replacing certificates is supported in IBM Cloud Private with OpenShift, but not with other installations or services.

References: [1] https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/manage_cluster/replace_cert.html  [2] https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/manage_cluster/cluster_certificates.html

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.

To limit and secure integrations with an external service, the Cloud Pak for Business Automation operator root CA signer certificate should be provided to the external service provider to be configured. This establishes a trusted relationship between the Cloud Pak for Business Automation capability on OpenShift with the external service.

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

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

When backing up data within a multiple-zone cluster, it is important to make regular backups for the active zone only. This ensures that the data is up-to-date and any changes made in the other zones are not lost if something goes wrong.

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

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.