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

The Kubernetes master API server stores secrets in the etcd directory. etcd is a key-value store that is used to store, replicate, and manage the Kubernetes cluster state. The other options are not related to this process.

References: [1] https://kubernetes.io/docs/concepts/configuration/secret/  [2] https://coreos.com/etcd/docs/latest/

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.

When setting up a demo environment an identity provider may not be known. In this case, htpasswd can be used to replace the default admin user with a simple identity provider. Htpasswd is an Apache utility for creating and updating user authentication files for the Apache web server. It uses a combination of plaintext passwords and a hashing algorithm to store its credentials.

References: [1] https://httpd.apache.org/docs/2.4/programs/htpasswd.html  [2] https://httpd.apache.org/docs/2.4/howto/auth.html#gettingstarted

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

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

• B. Content Management Interoperability Services (CMIS): This component provides a web service interface that allows other systems to interact with the FileNet system. This can be useful for organizations that need to integrate the FileNet system with other systems, such as line-of-business applications or other ECM systems.
• E. Content Platform Engine: It is IBM's ECM platform that allows organizations to store, manage, and access large amounts of unstructured content such as images, documents, and videos. It provides a number of services such as security, retention, and search, and can be integrated with other IBM products such as FileNet.

When deploying License Service Reporter, the summary card additionally shows a View license usage link. This link leads to the License Service Reporter user interface that presents the license usage of your products within the reporting period for a multi-cluster environment. The license usage presented is Average Daily Usage, which is the average number of licenses used per day in the reporting period.

References: [1] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/com.ibm.cic.agent.lmgr.user/license_usage.html  [2] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/com.ibm.cic.agent.lmgr.user/view_license_usage.html

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/

To install Operational Decision Manager Standalone CNCF for production, two steps are required:

• Download the container images: The container images are necessary for the installation, and they need to be downloaded and made available to the cluster.
• Download the archive from IBM Passport Advantage (PPA) to get the Helm chart: The Helm chart contains the configuration information necessary to install and deploy the ODM. It can be downloaded from the IBM Passport Advantage website.

It's important to note that other steps such as pruning existing deployment snapshots from the database, deleting the container registry image pull secret, or adding the resAdmin user to the IBM Entitled registry are optional and not required for the installation of Operational Decision Manager Standalone CNCF for production.