C1000-173 Practice Questions

IBM Match 360 is a master data management (MDM) service within IBM Cloud Pak for Data. Its primary function is to consolidate data from disparate sources to create a single, trusted 360-degree view of master data entities (e.g., customers, products). A key outcome of this process is the ability for data stewards and analysts to use the Master Data Explorer interface. This interface provides tools to search, view, and analyze the consolidated master data, including statistics about the data entities and graphical representations of their relationships, which allows users to explore and understand the master data.

A. This describes a conversational AI or natural language interface, which is the core function of IBM Watson Assistant, not IBM Match 360.

B. This describes data virtualization, where data is accessed from multiple sources without being moved. This capability is provided by the Watson Query service in Cloud Pak for Data.

C. This describes a business intelligence (BI) and analytics platform for creating AI-driven dashboards. This is the primary function of IBM Cognos Analytics.

1. IBM Cloud Pak for Data 4.8 Documentation

"IBM Match 360". This document outlines the core capabilities of Match 360. The section on "Exploring master data" states: "The master data explorer enables data engineers and data stewards to search

view

and analyze your master data... View a graph of the relationships between records." This directly supports the correct answer (D) by describing the analysis and exploration features.

2. IBM Cloud Pak for Data 4.8 Documentation

"Watson Query". The overview states: "With the Watson Query service on Cloud Pak for Data

you can have a single point of access to all your data sources... without having to move or replicate data." This confirms that option (B) describes Watson Query

not Match 360.

3. IBM Cloud Pak for Data 4.8 Documentation

"Watson Assistant". The service description states: "Build conversational interfaces into any application

device

or channel." This confirms that option (A) describes Watson Assistant.

4. IBM Cloud Pak for Data 4.8 Documentation

"Cognos Analytics". The overview describes the service as a "business intelligence solution that empowers users with AI-infused self-service capabilities" to "create compelling dashboards and reports." This confirms that option (C) describes Cognos Analytics.

In IBM Cloud Pak for Data, platform-level administrative privileges do not automatically grant access to the functionalities within specific service instances like IBM Match 360. Access control for Match 360 is managed through service-specific user groups (Data Engineer, Data Steward, Publisher User, and Entity Viewer). To obtain access, a Cloud Pak for Data administrator, like any other user, must be explicitly added to one of these predefined user groups associated with the Match 360 service instance. This adheres to the principle of least privilege, ensuring that access to sensitive master data is strictly controlled and audited.

A. Each user who is assigned to a service group has access.

This statement is generally true but is not the most precise answer to how an administrator obtains access. It describes the result of being in a group, not the requirement for the administrator.

B. Each user is automatically granted read access.

This is incorrect. Access is not granted automatically to any user; it must be explicitly assigned to a specific role to prevent unauthorized access to potentially sensitive master data.

C. Administrative users automatically have access.

This is incorrect. Cloud Pak for Data maintains a separation between platform administration and service-level access. An administrator role does not confer inherent permissions for all installed services.

1. IBM Cloud Pak for Data 4.8 Documentation

"Giving users access to IBM Match 360 with Watson": This official document outlines the procedure for granting access. It states

"To give users access to IBM Match 360

you must assign them the appropriate user role within the service." It then details the process of adding users to the service instance and assigning them to roles like Data Engineer or Data Steward

confirming that access is not automatic

even for administrators.

Reference Location: IBM Cloud Pak for Data 4.8 -> Services -> IBM Match 360 with Watson -> Administering -> Giving users access to IBM Match 360 with Watson.

2. IBM Cloud Pak for Data 4.8 Documentation

"Predefined roles and permissions": This section details the platform-level roles. The "Administrator" role is defined as having permissions to manage the platform

users

and service instances

but it does not grant automatic access into those services. This supports the concept that service-level access is managed separately.

Reference Location: IBM Cloud Pak for Data 4.8 -> Administering Cloud Pak for Data -> Managing users -> Predefined roles and permissions.

3. IBM Cloud Pak for Data 4.8 Documentation

"User roles and permissions for IBM Match 360": This page explicitly lists the four user groups (Data Engineer

Data Steward

Publisher User

Entity Viewer) and the permissions associated with each. It reinforces that access and capabilities within Match 360 are entirely dependent on membership in one of these groups.

Reference Location: IBM Cloud Pak for Data 4.8 -> Services -> IBM Match 360 with Watson -> Administering -> User roles and permissions.

The IBM Cloud Pak for Data Audit Logging Service is built upon the Fluentd data collector. It utilizes Fluentd's capabilities to gather audit records generated by various Cloud Pak for Data services. For external integration, it uses Fluentd's output plugins to forward these records to Security Information and Event Management (SIEM) systems. This architecture allows for flexible configuration to route audit data to one or more external monitoring solutions like QRadar or Splunk.

A. Not all services generate audit records. While most core services do, the official documentation provides a specific list of services that support audit logging, implying it is not a universal feature across every component.

C. Different connection methods can be used for multiple SIEM systems. The underlying Fluentd configuration allows for separate directives, enabling, for example, one SIEM to receive logs via syslog and another via an HTTP endpoint.

D. The documentation explicitly mentions and provides configuration examples for IBM QRadar and Splunk. While other SIEMs can be integrated using standard protocols, Log360 is not listed as an officially supported solution.

1. IBM Cloud Pak for Data 4.8 Documentation

"Exporting Cloud Pak for Data audit records to your security information and event management solution."

This document states

"The audit logging service uses Fluentd to forward and export audit records." This directly supports the correct answer (B). It also provides configuration examples for QRadar and Splunk

but not Log360

which refutes option D. The ability to add multiple

distinct configurations in the zen-audit-fluentd-forwarder-config ConfigMap refutes option C.

2. IBM Cloud Pak for Data 4.8 Documentation

"Audit logging in Cloud Pak for Data."

This section mentions

"By default

audit logging is enabled for all services that are installed. However

only the services that generate audit events will send records to the audit logging service." This

along with the specific list on the "Services that generate audit records" page

confirms that not every single component necessarily generates logs

refuting the absolute claim in option A.

The primary purpose of the IBM Data Replication service, particularly within IBM Cloud Pak for Data, is to capture data changes from a source system and apply them to a target system in near real-time. This continuous process ensures data is synchronized across different locations or platforms. This synchronization is a key method of data integration, supporting use cases such as high availability, disaster recovery, data migration, and offloading reporting workloads from production systems.

A. This describes the function of a database activity monitoring tool, such as IBM Security Guardium, not a data replication service.

B. This describes data virtualization or federation, which is the primary purpose of the IBM Data Virtualization (Watson Query) service, not Data Replication.

D. This describes the core function of an ETL (Extract, Transform, Load) tool like IBM DataStage, which focuses on complex data transformation and cleansing.

1. IBM Cloud Pak for Data 4.6 Documentation

"Data Replication overview": "With the Data Replication service

you can replicate data between source and target databases in near real time. Data Replication provides a replication solution for high-availability and disaster-recovery (HADR) scenarios

live reporting

and migrating data between data centers and to the cloud." This directly supports the concept of synchronizing and integrating data.

2. IBM Cloud Pak for Data 4.6 Documentation

"DataStage overview": "Use DataStage to design

develop

and run jobs that transform and cleanse data." This clearly distinguishes the purpose of DataStage (transformation) from Data Replication.

3. IBM Cloud Pak for Data 4.6 Documentation

"Data Virtualization overview": "With the Data Virtualization service

you can use a single query to get data from multiple sources in the cloud and on-premises without moving the data." This confirms that providing a unified view without moving data is the role of Data Virtualization.

IBM Data Virtualization provides a single, unified query interface across multiple, heterogeneous data sources without physically moving the data. A primary benefit of this approach is the ability to establish a centralized point for data access and governance. Administrators can define and enforce security policies, access controls, and data masking rules on virtual tables within the Data Virtualization service, ensuring consistent governance across all underlying data sources from a single location. This simplifies security management and ensures compliance.

A. Data can be copied to the platform quickly and easily.

This is incorrect. The core principle of data virtualization is to query data in-place, thereby avoiding the need to copy or move it, which saves time and storage costs.

B. Workloads can bypass data source security for faster execution.

This is incorrect. Data Virtualization respects and integrates with source security. It does not bypass security controls; instead, it provides an additional layer of centralized security and governance.

C. Discover and classify sensitive information.

This is incorrect. While governed virtual data can be profiled, the primary service for automated discovery and classification of sensitive information in IBM Cloud Pak for Data is Watson Knowledge Catalog.

1. IBM Cloud Pak for Data Documentation - Data Virtualization Overview: "With the Data Virtualization service

you can use a single connection to any data source to query all of your data... You can use Data Virtualization to govern access to your data in a central

secure

and monitored environment." This directly supports the concept of centralized governance (Answer D).

2. IBM Cloud Pak for Data Documentation - Governing virtual data: "You can govern virtual data in Watson Knowledge Catalog in the same way that you govern other data assets... When you virtualize data

the virtual tables are automatically added to the default catalog." This shows that governance is a key feature

but also distinguishes the virtualization service from the cataloging service (Why C is incorrect).

3. IBM Cloud Pak for Data Documentation - Data Virtualization Overview: "Data Virtualization is designed to query data sources directly and to minimize data movement." This statement explicitly contradicts the idea of copying data (Why A is incorrect).

The Watson OpenScale API is designed for AI model governance and monitoring. Its primary capability is to track and measure the outcomes of AI models in production. This includes evaluating model quality (e.g., accuracy), detecting data and accuracy drift over time, and ensuring fairness by identifying and mitigating biases in model predictions against protected attributes like age or gender. It also provides explainability for individual transactions, helping stakeholders understand why a model made a specific decision. These functions are crucial for building trust and transparency in AI systems.

A. Building conversational interfaces is the primary function of IBM Watson Assistant, not Watson OpenScale.

B. Managing data-related assets is a core capability of IBM Watson Studio and IBM Watson Knowledge Catalog, which are used for model development and data governance.

C. Extracting answers from business documents is the main purpose of IBM Watson Discovery, which uses natural language processing for insight generation.

1. IBM Cloud Documentation. (2024). Getting started with Watson OpenScale.

Section: "What is Watson OpenScale?"

Content: "IBM Watson OpenScale tracks and measures outcomes from your AI models

and helps ensure they remain fair

explainable

and compliant... Watson OpenScale detects and helps mitigate model drift and bias..." This directly supports the capabilities of measuring outcomes and ensuring fairness.

URL: https://cloud.ibm.com/docs/openscale?topic=openscale-getting-started

2. IBM Cloud Documentation. (2024). Watson OpenScale API Reference.

Section: "API introduction" and various endpoints like /v2/evaluations and /v2/monitors.

Content: The API reference details programmatic access to configure fairness monitors

quality monitors

and drift monitors

and to retrieve evaluation results. This confirms that the core capabilities described in option D are exposed via the API.

URL: https://cloud.ibm.com/apidocs/watson-openscale

3. IBM Cloud Documentation. (2024). Fairness evaluations.

Section: "Understanding fairness"

Content: "Watson OpenScale checks your model for bias to ensure fair outcomes across different groups. The fairness evaluation checks whether your model is producing biased outcomes." This document explicitly details the fairness measurement capability.

URL: https://cloud.ibm.com/docs/openscale?topic=openscale-enabling-fairness

Business lineage in IBM Knowledge Catalog provides a graphical representation of the relationships between various assets, such as business terms, data assets, reports, and governance artifacts. This complex network of relationships and the flow of data are stored, managed, and rendered using the underlying knowledge graph technology. The knowledge graph serves as the foundational repository for the metadata and relationships that are visualized in the business lineage report. Therefore, this component must be enabled during installation to support the business lineage feature.

A. Automated metadata lineage: This feature imports detailed technical lineage from external sources into the catalog; it populates the knowledge graph but is not the core rendering component itself.

C. Data graph: This is a generic industry term. The specific IBM component that manages and renders these relationships within IBM Knowledge Catalog is officially termed the "knowledge graph".

D. Data quality: This component is used for assessing, monitoring, and improving the quality of data assets, a function distinct from visualizing the flow and lineage of data.

1. IBM Cloud Pak for Data 4.8 Documentation

"Lineage": "Lineage information is stored in the knowledge graph along with other metadata about assets... Business lineage shows a simplified

high-level view of lineage information that is most interesting to business users." This statement directly links the knowledge graph to the storage and presentation of business lineage.

2. IBM Cloud Pak for Data 4.8 Documentation

"Installing Watson Knowledge Catalog": The installation guide specifies the services that constitute the Watson Knowledge Catalog. The advanced features

including governance and lineage

rely on the core services which include the underlying graph database technology that powers the knowledge graph. The "wkc-gov-ui" service

responsible for the governance UI including lineage

depends on these core data services.

3. IBM Cloud Pak for Data 4.8 Documentation

"Managing business lineage": This section details how to work with business lineage reports. The entire functionality described—visualizing asset flows

adding details

and exporting—is powered by the data stored and organized within the knowledge graph.

The primary purpose of profiling data in IBM Data Refinery is to analyze and understand its content and quality. Profiling automatically generates statistics and frequency distribution charts for each column of the dataset. This allows data professionals to quickly identify patterns, outliers, missing values, and other data quality issues. By examining these profiles, users can validate the data's integrity and determine the necessary cleansing and shaping operations required before using it for analysis or machine learning.

B. Loading data into a different location is the function of running a Data Refinery flow to save the transformed output, not the purpose of the profiling step.

C. Creating data backups is a data storage and administration task for disaster recovery, which is outside the scope of Data Refinery's data preparation functions.

D. While profiling generates basic visualizations like histograms, its main goal is data validation and quality assessment, not creating comprehensive business intelligence dashboards.

1. IBM Cloud Pak for Data Documentation

"Refining data."

Section: Profiling and visualizing data

Content: The documentation explicitly states

"Profile your data to validate it. The first step in refining data is to understand it by profiling it. The Profile tab shows you the frequency distribution of the data in each column and statistics for string and numeric data." This directly links the purpose of profiling to data validation.

2. IBM Cloud Pak for Data Documentation

"Data Refinery operations."

Section: FREQUENCY

Content: This section describes an operation that is a core part of profiling. It details how viewing the frequency of values in a column helps "get a better understanding of your data and to help you clean it." This supports the idea that profiling's purpose is to understand and validate for cleansing.

In IBM Watson Pipelines, the Error Handling feature is the designated component for managing failures within a pipeline node. When configuring a node, such as "Run DataStage job," the "Error handling" tab allows a user to define the pipeline's behavior upon encountering an error. This includes options like terminating the entire pipeline immediately, continuing the run despite the error, or proceeding down a specific conditional path. This mechanism provides robust control over the pipeline's execution flow in case of job failures.

A. Fault Settings: This is a generic term. The specific feature within Watson Pipelines for managing node failures is explicitly named "Error Handling," not "Fault Settings."

B. Default Control: This term is too general and does not represent a specific, named component or setting for managing errors within the Watson Pipelines service.

D. Process Termination Window: This describes a potential action or outcome (termination) that can be configured within Error Handling, but it is not the name of the component itself.

1. IBM Cloud Pak for Data 4.8 Documentation

"Configuring pipeline nodes": Under the "General node settings" section

it describes the "Error handling" tab. It states

"Configure settings for handling errors for the node. You can specify what to do if the node returns an error

for example

you can specify to stop the pipeline." This directly confirms "Error Handling" as the correct component.

2. IBM Cloud Pak for Data 4.8 Documentation

"Run DataStage job": This section details the configuration for a DataStage job node within a pipeline. It explicitly lists "Error handling" as a configurable property to manage how the pipeline reacts if the DataStage job fails during execution.

Db2 Big SQL on IBM Cloud Pak for Data provides a REST (Representational State Transfer) API endpoint for application interaction. This allows developers to programmatically submit SQL statements, monitor the status of their execution, and retrieve the results using standard HTTP methods. This RESTful interface is a common method for integrating modern applications with data services, offering a stateless and scalable way to interact with the Db2 Big SQL engine without requiring traditional database drivers like JDBC or ODBC.

B. System Local Efficient Endpoint Pathways (SLEEP): This is a fabricated acronym and does not correspond to a recognized technology or standard for application endpoints in this context.

C. Simple Normalized Optimum Representative Endpoint (SNORE): This is a fictitious term created as a distractor and does not represent a valid type of application endpoint.

D. Dynamic Representative Endpoint Activation Mobility (DREAM): This is also a fabricated acronym and is not a real technical term for an application interaction endpoint.

1. IBM Cloud Pak for Data 4.8 Documentation: The official documentation explicitly details the REST API for Db2 Big SQL. It describes how to submit SQL jobs via a POST request to the /bigsql/v1/sqljobs endpoint.

Source: IBM. (2023). Cloud Pak for Data 4.8 Documentation

"Db2 Big SQL service"

section "Submitting SQL statements to Db2 Big SQL by using the REST API".

Details: The documentation provides the endpoint structure (POST /bigsql/v1/sqljobs)

request body format (e.g.

{"sqlstatement":""})

and expected responses

confirming the use of a REST endpoint.

2. IBM Cloud Pak for Data 4.8 Documentation: The API reference for Db2 Big SQL provides comprehensive details on all available REST endpoints

including those for managing the service and executing queries.

Source: IBM. (2023). Cloud Pak for Data 4.8 Documentation

"API reference for Db2 Big SQL".

Details: This section serves as the primary reference for developers

listing all REST API calls

parameters

and data structures for interacting with Db2 Big SQL.