IBM Business Automation Workflow V20.0.0.2 Using Workflow Center Development Free Sample Questions

This is the most practical and effective solution within the given constraints. BAW and its underlying database support transaction logging. By placing these logs on a synchronously replicated, low-latency storage device (which is feasible across data centers for smaller log files), the application can recover the transactions that occurred after the last asynchronous database snapshot. This meets the 15-minute RPO by reconciling the data gap without the high cost and latency issues of full synchronous database replication. Increasing async frequency (A) doesn't guarantee zero data loss. A two-phase commit (B) is extremely complex to implement and manage. Container-native synchronous storage (C) is a valid but much larger architectural change and might violate the 'no synchronous replication' network constraint for large volumes.

An event-based gateway is the correct pattern here. It waits for one of several events to occur. In this scenario, each of the three tasks would have a rejection outcome that fires a signal or message event. The event-based gateway catches the first rejection event that fires, immediately routing the process to termination without waiting for the other parallel tasks to complete. Using a parallel join gateway (A) would force the process to wait for all three reviews, even if one rejected early, which is inefficient. An inclusive gateway (B) is also a waiting pattern. A complex gateway (D) is overly complicated for this common requirement.

The Page Designer and its underlying Carbon framework provide built-in responsive settings for UI components. The 'Screen Size Behavior' property is the declarative, out-of-the-box way to control component visibility based on screen size (e.g., Phone, Tablet, Desktop). This is the most maintainable and recommended approach as it doesn't require custom code (A), avoids duplicating UIs (B), and handles responsiveness on the client-side where it belongs (C).

The 'Folder Identifier' property is the specific configuration setting on the Document List coach view that is used to provide the unique ID of the folder in the external ECM system whose contents should be displayed. The Search Query is used for more complex, property-based searches. Document Types filter the results, and Displayed Properties configures the columns shown.

The symptom of multiple sequential Ajax calls points directly to a 'chatty' UI design where individual components fetch their own data independently. This creates significant overhead from network latency and server round-trips. The best practice is to aggregate these calls into a single, coarser-grained service that runs once, fetches all the data needed for the page, and populates a comprehensive business object. The UI controls can then be bound to different parts of this single object, eliminating the multiple round-trips. While network latency (A) and server power (B) can be factors, the design pattern is the root cause here. Using heritage human services (D) is not a solution for performance issues in client-side services.

False. The 'Leave' option allows currently running instances to continue to completion using the old snapshot's definition. All new instances will be created from the newly deployed snapshot. The 'Migrate' option is used to move running instances to the new snapshot, and the 'Delete' option would terminate them.

Case Builder provides declarative preconditions for starting tasks. The specific condition 'A document of a specific class is filed in the case' is the standard, out-of-the-box way to implement this requirement. This allows the developer to select the 'Signed Contract' document class and the task will not become available until a document of that type is filed. Using scripts or external services is unnecessary and more complex for this common pattern.

A Team Filter Service is the correct component for this requirement. Its purpose is to take a list of potential users (e.g., all members of the 'Senior Adjusters' team) and apply custom logic to filter or sort that list to determine the final assignee(s). A Team Retrieval Service is used to find the initial list of users, not to filter it based on workload. An Expert Team is for routing based on specific expertise. A simple Team binding is static.

This is the standard and most robust pattern for handling events within a reusable Coach View. The view defines configuration options that act as event handlers. The containing Coach binds these configuration options to Ajax services. Inside the Coach View's change event, the code checks which control's data has changed and invokes the appropriate configuration option function (e.g., this.context.options.onCountryChange()). This decouples the view from the specific service being called, making it highly reusable. Loading all data upfront (A) is inefficient. Manually firing boundary events (B) is incorrect for this use case. Using a single dataChange service (D) is less flexible and doesn't scale well.