C1000-194 Exam Dumps - IBM Data and AI: Data and AI Questions and Answers

The correct answer is C. IBM Robotic Process Automation distinguishes bots by their operating mode. Attended bots work alongside human users and are typically launched on demand to help complete repetitive or structured tasks during a user session. They support productivity by assisting the user in real time, often through IBM RPA Launcher or user-triggered execution. Unattended bots do not require human help at execution time. They are scheduled, orchestrated, or called through APIs and commonly run on servers or virtual machines using configured credentials and runtime capacity. Option A is incorrect because attended status is not defined by cognitive capability. Option B reverses the definitions. Option D incorrectly implies that attended bots handle independent large-scale workloads while unattended bots are restricted to narrow applications. In solution architecture, attended automation is best suited for front-office assistance and human-in-the-loop productivity, while unattended automation is best suited for back-office, scheduled, integrated, and autonomous process execution. References/topics: IBM RPA, attended automation, unattended automation, RPA Launcher, Bot Runtime, scheduled and orchestrated scripts.

The correct answer is C: Resource Registry and Business Automation Navigator. The Foundation Pattern provides the baseline platform services that are included with Cloud Pak for Business Automation deployments. IBM deployment guidance identifies Business Automation Navigator and Resource Registry as foundation components that are installed always. Navigator provides the unified business-user access layer for content and automation applications, while Resource Registry supports discovery and registration of automation resources across the platform. Business Automation Studio and Application Engine are foundation-related components, but their installation depends on the selected capability pattern or optional component. Business Automation Insights is also not always installed; it is included only when selected directly or required by a combined capability that activates insights/event-processing services. Therefore, the always-present foundation pair is Resource Registry and Business Automation Navigator. References/topics: CP4BA Foundation Pattern, Resource Registry, Business Automation Navigator, capability-pattern dependencies, production deployment planning.

The correct answer is A: Operational Decision Manager. Loan approval is a classic operational decision-management use case because approval, rejection, referral, pricing, eligibility, risk-tiering, and compliance logic can be expressed as business rules and decision tables. Operational Decision Manager enables businesses to respond to real-time data by applying automated decisions, and business and technical users can externally develop and manage decision logic used by operational systems. ODM decision management supports intuitive rule editing, collaborative development, scalable deployment, and integration with production systems. FileNet Content Manager would store loan documents and supporting evidence, but it does not automate approval rules. Business Automation Workflow can orchestrate the loan process, assign tasks, and manage exceptions, but it is not the most suitable capability for business-rule authoring and decision execution. ODM is therefore the best fit for scalable, governed, user-friendly loan-decision automation. References/topics: Operational Decision Manager, decision services, business-rule management, rule authoring, automated loan decisions.

The correct answer is A. In a containerized Cloud Pak for Business Automation deployment, high availability is achieved through Kubernetes and Red Hat OpenShift platform services rather than traditional WebSphere topology components. IBM documentation contrasts traditional and containerized HA configurations and identifies the router in Red Hat OpenShift or Kubernetes as the load-balancing mechanism for the container deployment model. This is distinct from traditional on-premises WebSphere deployments, where IBM HTTP Server, WebSphere plug-ins, and node agents are more relevant. Option B is therefore associated with the traditional load-balancer model, not the unique containerized feature. Option C is incorrect because WebSphere node agents are not the Kubernetes-native health-management mechanism. Option D similarly belongs to the traditional WebSphere plug-in/session-affinity approach. In CP4BA on OpenShift, availability is instead supported by pods, services, routes, replicas, liveness/readiness probes, OpenShift routing, session affinity where configured, and deployment across worker nodes or availability zones. The router-based load-balancing model is therefore the container-specific HA answer. References/topics: CP4BA high availability, container deployment, OpenShift router, Kubernetes load balancing, session affinity differences.

For a highly available Cloud Pak for Business Automation deployment, the priority is to deploy control planes and worker nodes across multiple availability zones. This design reduces single-zone failure risk and enables the OpenShift platform to reschedule workloads, maintain quorum, and recover services when infrastructure in one zone becomes unavailable. Keeping hardware in one availability zone improves locality but creates a fault-domain concentration risk, so option A is the opposite of the recommended HA posture. IBM HTTP Server is relevant to traditional WebSphere-based topologies, not the primary load-balancing mechanism for Cloud Pak container deployments. Node agents are also associated with traditional WebSphere Network Deployment rather than Kubernetes-native pod supervision. In containerized CP4BA, high availability is achieved through pod distribution, resilient storage, OpenShift scheduling, router/load-balancer behavior, replicas, and fault-domain separation. A correct architecture separates failure domains across control-plane and worker infrastructure. References/topics: High availability topology, Red Hat OpenShift fault domains, Storage HA, CP4BA HA versus traditional on-premises HA.

The correct answer is D: Common Web UI Service. Cloud Pak foundational services provide shared platform functions such as identity management, licensing, certificate management, business teams, and platform user-interface services. Common Web UI Service, implemented by the common UI operator, is the foundational service associated with access to the cluster Administration Hub, or console. This service is separate from the Cloud Pak Platform UI, also known as Zen UI, which provides a single role-based user interface for Cloud Pak capabilities. The Administration Hub function is specifically tied to Common Web UI Service, not to a generic Admin Service or Console Service. Option A is also not the official service name in the Cloud Pak foundational services taxonomy. From an architectural perspective, this distinction matters because foundational services are installed and managed as operators, and access to platform administration features depends on those shared operators being present and healthy. References/topics: Cloud Pak foundational services, Common Web UI Service, Administration Hub, Cloud Pak Platform UI / Zen UI.

The correct answer is B. Business Automation Navigator is the browser-based user experience for working with content and automation applications in Cloud Pak for Business Automation. Navigator enables business users to work with content from various sources and use business automation applications built to help with daily work. IBM's architecture guidance describes IBM Business Automation Navigator as a browser-based interface for working with content from various sources and accessing business applications, dashboards, content features, custom plug-ins, and third-party applications. Option A is too narrow because viewing or annotating content may be one function of a content experience, but it does not define Navigator. Option C is wrong because Navigator is not a thick client and is not the processing engine for all document types. Option D is also incorrect because Navigator is not positioned as an offline hybrid client. Architecturally, Navigator is the unified business-user surface that brings together repository access, content operations, automation application access, and extensibility through plug-ins. References/topics: Business Automation Navigator, browser-based interface, unified work experience, content access, business applications, dashboards, plug-ins.

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.

A lookup occurs during Verification. In IBM Datacap, verification is the point at which captured and recognized data is reviewed, corrected, validated, or enriched before the batch is exported to downstream systems. Lookup actions are typically used to validate field values against an external source, such as a database, REST service, SOAP service, or application-specific reference table. For example, an operator can enter partial known data in a verify task field, invoke a lookup, select the correct returned record, and populate or validate related fields. This pattern fits the verification phase because the operator is resolving uncertain or incomplete captured values while the document is still inside Datacap's quality-control workflow. Profiler is more associated with identifying or structuring documents, VScan is associated with scanning or virtual scanning ingestion, and Export is the final handoff after validation. Therefore, Verification is the precise task where interactive lookup behavior belongs. References/topics: Datacap verification tasks, lookup actions, field validation, database lookup, operator correction and enrichment.

The correct answer is D. Workflow optimization in Business Automation Workflow depends heavily on modular, reusable design. Reusable components reduce duplication, improve maintainability, and make workflows easier to scale, test, troubleshoot, and evolve. Reusable views are collections of user interface widgets that can be composed from other views, bindings, layouts, and behaviors. Workflow modernization in Cloud Pak for Business Automation also includes reusable automation services that can be published and called from workflows. This architecture allows common functions, such as approvals, notifications, validation, enrichment, or user-interface fragments, to be built once and reused consistently across multiple workflow automations. Option A is incorrect because testing remains essential even for small workflow changes, especially in regulated or production environments. Option B weakens automation value by replacing rule-based assignment with manual routing. Option C is the opposite of the recommended practice because non-modular workflows become hard to govern and change. References/topics: Business Automation Workflow optimization, reusable views, reusable automation services, modular workflow design, maintainability and scalability.