IBM C1000-173 Practice Exam Questions & Answers

Configuring access to a Git repository in Cloud Pak for Data projects allows teams to collaborate on code, notebooks, and assets while benefiting from version control and branching. This setup ensures that all project files can be tracked, reverted, or merged, enabling collaborative development and continuous integration workflows. It is not used for model deployment management (B) or visualization enhancements (C). Option D is unrelated to the actual purpose of Git integration.

In Watson Pipelines within IBM Cloud Pak for Data, error management is handled by the Error Handling component. This feature allows developers and pipeline administrators to define how pipeline failures are processed---whether to stop execution, continue, or trigger alternate flows. It ensures controlled behavior in response to job failures, particularly in complex ETL pipelines like those built with DataStage. Error Handling is a configurable element of pipeline orchestration and is typically used to enhance fault tolerance and control error propagation in production workflows.

To virtualize files that reside in shared directories (e.g., NFS, SMB, or other on-premises sources), IBM Data Virtualization uses a remote connector agent. This remote connector is installed and executed on the source server to enable secure access and metadata extraction. The service does not scan networks automatically nor rely on FTP. Directly adding file shares via the UI is not sufficient without the backend connector in place, which acts as a secure communication bridge.

IBM Cloud Pak for Data includes built-in Data Protection Rules to enforce access control on sensitive data, such as PII. These rules are integrated directly into services like IBM Data Virtualization, Data Privacy, and IBM Knowledge Catalog. When analysts or applications access data through these services, the platform automatically masks, obfuscates, or restricts access to sensitive fields based on the defined policies. This ensures compliance with data privacy regulations and organizational security policies without manual intervention.

In IBM Data Virtualization, caches must be manually defined by administrators. While monitoring and query performance statistics can guide where caching would be beneficial, the creation and configuration of caches (e.g., refresh schedules and scope) are manual tasks. There is no automated cache creation mechanism (A), nor are DataStage flows used for cache maintenance (B). Suggestions based on statistics (D) may assist administrators, but they do not automatically create the caches.