During a design review, an architect asks which choice best matches the IBM guidance. What is the best way to handle Data manager while staying aligned with the certification objectives?
Select an answer to reveal the explanation.
Short Explanation and Infographic
In watsonx.data, Data Manager provides the administrative interface for catalog operations: registering new data sources, browsing existing schemas and tables, managing table metadata and tags, and performing table-level governance operations. It surfaces the same metadata that query engines read, so changes in Data Manager take effect immediately for all consumers. Bypassing Data Manager to modify catalog metadata directly risks corrupting the governance layer that downstream consumers depend on.
Full explanation below image
Full Explanation
The correct answer is option B: Use Data manager to browse, register, organize, and manage lakehouse data assets.. This aligns with IBM's Platform operations and administration guidance, which emphasizes use data manager to browse, register, organize, and manage lakehouse data assets as the recommended approach for production deployments. Option A (Use Data manager only for user password resets) is incorrect because it either bypasses IBM's recommended architecture or introduces operational risk that the correct approach is specifically designed to avoid. Option C (Manage table metadata through email requests) is incorrect because it either bypasses IBM's recommended architecture or introduces operational risk that the correct approach is specifically designed to avoid. Option D (Avoid registration so data remains discoverable) is incorrect because it either bypasses IBM's recommended architecture or introduces operational risk that the correct approach is specifically designed to avoid. Understanding this distinction is critical for the C9007300 exam: IBM watsonx.data is designed to enforce governance, performance, and operational best practices through its built-in architecture, and the correct answers consistently reflect those architectural constraints rather than shortcut alternatives.