A senior engineer reviews the current plan and notices that one key control is missing. 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
Here's the deal: Data Manager in watsonx.data is your digital librarian — it's the place where you register, browse, organize, and manage all your lakehouse data assets. Think of registering a table like checking a book into the library system: until it's cataloged, nobody can find it. Data Manager isn't for password resets or user admin — it's purely about data asset lifecycle management.
Full explanation below image
Full Explanation
The correct answer is to use Data Manager to browse, register, organize, and manage lakehouse data assets. Within the watsonx.data console, Data Manager provides a GUI for registering external buckets, managing Iceberg table registrations, organizing schemas and catalogs, and reviewing asset metadata. Option A (password resets) is wrong because user authentication is handled by IBM Cloud IAM or the platform's identity provider, not Data Manager. Option C (email requests for metadata) is wrong because it creates an untracked, manual process that undermines the catalog's role as the single source of truth. Option D (avoiding registration) is wrong because unregistered data assets are invisible to governed SQL engines and cannot have access controls, lineage, or policies applied to them. Proper registration is the entry point for every governance and discovery capability in the platform.