The correct answer is C: Create task model artifacts. Business Automation Workflow projects are collections of artifacts used to solve business process and case-management problems. In BAW, tasks are core workflow constructs because work is decomposed into human tasks, participating tasks, case activities, process activities, services, and related assignment logic. A BAW project is a set of artifacts that share the same lifecycle and are grouped to solve a business problem. Task-model creation in BAW Advanced allows task templates or task instances to be built from task model classes and associated artifacts, supporting human or participating task execution. Option A is plausible because service flows are also developed in BAW, but the exam item focuses on the common workflow-project activity most aligned with BAW's task-centric modeling capability. Option B belongs to decision modeling, typically ADS or DMN-oriented rather than BAW project development. Option D is not a standard phrasing for BAW development; KPIs are associated with monitoring and analytics rather than service artifact creation. References/topics: Business Automation Workflow projects, task artifacts, human tasks, task templates, workflow project lifecycle.

The correct answer is A. In Business Automation Navigator and the underlying IBM Content Navigator content experience, the full Search capability provides the broader and more complete search function set, while Simple Search provides a streamlined search box for fast keyword-driven content retrieval and filter refinement. Simple Search is designed to reduce complexity for end users by allowing keyword entry and metadata-driven result trimming, but it does not replace the full-featured search model used for more structured or advanced repository searches. Option B is incorrect because Simple Search is not inherently limited to five results; administrators can configure limits for returned results. Option C is directionally true as a usability statement, but the tested distinction is functional scope: full Search includes all functionality, while Simple Search is intentionally limited. Option D is too rigid because Simple Search can use full-text search and metadata-driven filters, not keyword-only behavior. References/topics: Business Automation Navigator search, IBM Content Navigator Simple Search, Search capabilities, Metadata-driven filters, Content-Based Retrieval.

The correct answer is A. Using asynchronous tasks or asynchronous service invocations for non-critical operations improves workflow responsiveness by decoupling the user-facing or critical path from work that does not need an immediate return value. Business Automation Workflow supports service flows and automation-service operations that can be invoked synchronously or asynchronously, and the design distinguishes service flows enabled for asynchronous invocation from those that invoke only synchronous operations. In solution architecture, this design prevents long-running integrations, notifications, enrichment calls, or background updates from holding up the main process thread or user interaction. Option B is unsafe as a general best practice because reducing logging indiscriminately weakens traceability, auditability, and troubleshooting. Option C is invalid because BAW relies on persistent state, process instance data, task data, and transactional storage. Option D is the opposite of the preferred pattern for non-critical work because synchronous tasks keep the caller waiting and can increase latency under load. References/topics: Business Automation Workflow, service flows, asynchronous invocation, workflow performance design, non-critical background operations.

The correct tool is Aspera. In IBM content-centric architectures, Aspera is used to optimize large-file movement where standard browser upload and download behavior can introduce latency, timeout exposure, and poor user experience. When integrated with FileNet P8 and Business Automation Navigator or IBM Content Navigator, Aspera supports efficient upload, download, and transfer of large documents. This is especially important for high-volume content workloads, media-heavy repositories, regulated document archives, and distributed users who need reliable transfer performance over WAN links. FileCatalyst and Signiant are also known file-transfer technologies, but they are not the IBM-documented integration path for FileNet and Navigator in this context. FTP/SFTP acceleration is too generic and does not represent the named IBM integration capability. Aspera is the IBM-aligned solution for high-speed, secure transfer of large content objects in repository-based workflows. References/topics: Business Automation Navigator, FileNet P8 content repositories, IBM Content Navigator components, Configuring Aspera for FileNet P8.

The correct answer is C. Workflow Automation in Cloud Pak for Business Automation is the capability that orchestrates multiple business processes, including straight-through processes, human-assisted processes, and case-management work, while providing visibility into each step. This definition captures both execution and control: workflow automation sequences work, assigns or delegates tasks, coordinates services, integrates systems, manages case or process state, and enables stakeholders to see where work is in the lifecycle. Option A is incorrect because CP4BA workflow authoring is model-driven and low-code, not focused on low-level programming. Option B is too narrow because Business Automation Workflow explicitly supports case management as well as structured process work. Option D is unrelated; storage management is an infrastructure concern, not the primary function of Workflow Automation. In architecture terms, Workflow Automation is the orchestration backbone that links people, systems, data, rules, and content into executable business operations with runtime visibility and governance. References/topics: Workflow Automation, Business Automation Workflow, process orchestration, human-assisted work, case management, visibility into each step.

The correct answer is C: Business Automation Application. In Cloud Pak for Business Automation, deployment is structured around capability patterns that are selected in the custom resource or deployment tooling. Production deployment documentation lists capability patterns such as Foundation, Automation Decision Services, Automation Document Processing, Automation Workstream Services, Business Automation Application, Business Automation Workflow, FileNet Content Manager, Operational Decision Manager, and Workflow Process Service Authoring. Business Automation Studio and Business Automation Navigator are important platform components, but they are not the capability pattern represented in this option set. Navigator is an always-installed foundation component; Studio is installed when required by selected authoring capabilities. Business Automation Insights is a foundation-related insights component that may be selected or activated by combined capabilities, but the answer choice that corresponds to a named deployable capability pattern is Business Automation Application. This pattern provides Application Engine and application-related services used to run business applications and external automation services. References/topics: CP4BA capability patterns, Business Automation Application pattern, Foundation components, deployment planning, custom resource pattern selection.

The correct answer is Task, Audit log, Error, and Decision points and rules. In IBM Content Collector, task routes define how collected content is processed, evaluated, logged, and handled when failures occur. A task performs a processing action, such as collecting, transforming, classifying, archiving, or otherwise acting on content. An audit log task records successful or unsuccessful execution details, supporting traceability and operational diagnostics. An error task route provides controlled handling for exceptions and failed processing paths. Decision points and rules introduce conditional routing so that documents can follow different processing paths based on metadata, document state, or defined conditions. Collector is not one of the four building blocks listed for main task routes in the answer set; it represents a functional role in ingestion, not the structural route element being tested. These elements define a governed, auditable processing path for content capture and disposition. References/topics: Content Collector, Task routes, Elements of a task route, Decision points and rules, Audit log task, Error task route.

The correct answer is C. A Business Automation Studio project is the organizing container for automation artifacts that share the same lifecycle and are grouped to solve a business problem. Projects are used to build, manage, share, and organize these assets. A project can represent different automation types depending on the installed capabilities, including business applications, workflow automations, decision automations, document-processing automations, and external automations. This project model gives solution teams a controlled workspace for creating, developing, testing, publishing, and deploying automation assets so they can be reused consistently across the platform. Option A is incorrect because Datacap is a document-capture product, while Business Automation Studio projects are broader CP4BA authoring constructs. Option B uses generic project-management language but does not describe the Studio project purpose. Option D is unrelated to the CP4BA project model and predictive lifecycle assignment. References/topics: Business Automation Studio, projects, automation assets, lifecycle grouping, business applications, workflow automations, decision automations.

The correct answer is B. In IBM decision-management tooling, Excel scenario files are a recognized mechanism for defining scenario data used to validate decision behavior through testing and simulation. The build experience for decision projects includes preparing decision logic so that it can be validated against defined input scenarios and expected outcomes. Scenario files contain input data and expected results, and users can generate Excel scenario file templates from valid rule projects or decision operations. This aligns with the exam intent: the build experience includes defining test scenarios in a business-friendly format that domain experts can understand and maintain. Option A is incorrect because JSON unit-test scenarios are not the tested activity. Option C is too generic and relates more to integration design than decision-project build validation. Option D is a development extension activity, not a normal decision build experience. Excel scenario-driven validation supports repeatable, auditable testing of decision behavior before deployment. References/topics: Decision services, testing and simulation, Excel scenario files, expected results, rule project validation, decision build validation.

The correct answer is D. Automation Decision Services is designed around Git-based collaboration for decision automations and decision services. Each decision automation can be connected to a remote Git repository, allowing team members to work collaboratively, isolate changes in branches, and share decision-service artifacts through a governed repository model. This supports modern change management because decision services are versioned, branched, reviewed, shared, and synchronized through Git rather than through legacy source-control technologies. CVS and Subversion are not the repository integration model used by ADS in Cloud Pak for Business Automation. A local Git repository alone is also insufficient because the integration requirement is collaboration with a remote repository configured through the platform's Git provider mechanism. In architecture terms, the Git provider becomes the persistence and collaboration backbone for decision automation assets, while Decision Designer provides the authoring experience. The repository connection also supports team development, publication, backup, and controlled promotion of decision-service changes. References/topics: Automation Decision Services, Decision automations, Git provider configuration, Remote Git repository, Branching and sharing decision services.