A consultant is advising a customer that wants a scalable implementation. The team is focused on SQL access. Which recommendation is most appropriate?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Think of it this way: getting data out of watsonx.data via SQL is like checking out library books through the front desk — you go through the catalog, the librarian verifies your card, and you get exactly the books you're authorized to borrow. Downloading raw object files is like sneaking into the back warehouse; bypassing metadata catalogs is like pulling books without checking them out. SQL engines + governed tables = the proper checkout process.
Full explanation below image
Full Explanation
The correct answer is to guide users to query governed lakehouse tables through supported SQL engines and interfaces. IBM watsonx.data provides SQL access through the console Query Workspace, JDBC/ODBC connections for BI tools (Tableau, Cognos, Power BI), and the Presto CLI for command-line use — all of which route queries through the governance layer. Option B (downloading raw object files) is wrong because it bypasses access control, returns unformatted binary data (Parquet/ORC), and provides no schema context for interpretation; it also creates an ungoverned data copy outside the platform. Option C (bypassing metadata catalogs) is wrong because the catalog is where table schemas, access policies, and column definitions live — queries without catalog routing would fail or return uninterpretable raw results. Option D (screenshots for data delivery) cannot be used by downstream applications or analytics tools and represents a manual, unscalable anti-pattern.