IBM C1000-148 IBM Cloud Pak for Business Automation v21.0.3 Solution Architect Exam Practice Test

Active summaries

Time series

Anonymization rules

Completed summaries

Decisionmaking for each step in a business workflow

Identification of missing steps in a business workflow for optimization

Recommendation of risk event based on predicted next step in a business workflow

Identification of a change in the business rules of the organization

In the events of the case A, the trace-id element is set to null.

The parent-trace-id of the workflow B is set to the trace-id of caseA

In the events of the case A, the parent-span-id element is set to null.

The trace-id elements of all events in the sequence have the same value.

The parent-span-id element of both the workflow B and the ODM rule C have the value of thespan-id

element of case A

Besides offering and relying party, each Cloud Pak for Automation application needs to have its own OpenID.

OpenID can be configured for offering party and relying party at any time.

Offering party and relying party are known to each other.

OpenID Connect is the only valid authentication scheme for User Management Service.

Calling the REST service in a service task as part of a service flow is dynamic and does not need service discovery.

Unlike SOAP web services, REST services do not have a "server" configuration entity.

Calling REST services through JavaScript can happen only after a corresponding external service has been defined through service discovery.

When a REST service URL changes, service discovery happens automatically to replace the existing service.

FileNet Content Manager

Workstream Services

Business Automation Workflow

Content Analyzer

Content Analyzer calls the FileNet call-back API.

FileNet periodically checks to see whether processing is done.

FileNet listens to the Content Analyzer JMS queue.

Content Analyzer stores the result documents to-dos.

Log in to the cluster and run the command to check status of any individual product.

Check the list of pods from which the License Service might not collect license usage.

Check if the License Service was successfully deployed on the cluster by using available tools.

Run health checks by the License Service and use the log service to monitor the log.

Decentralizing the compliance process at the document level

Connecting to a built-in compliance database for content management function

Automating the burden of paperwork and regulatory compliance by digitizing and managing documentation

Utilizing Robotic Process Automation task bots to query government compliance endpoints

To find human task summaries based on the time stamp field

To find process instance summaries based on the time stamp field

To distinguish active and complete summaries

To parse summaries to find details from activities and process instances