An analyst has been granted access to a governed catalog in watsonx.data and wants to explore its tables and run ad hoc SQL without installing any client software. What should they use?
Select an answer to reveal the explanation.
Short Explanation
Use the query workspace in the watsonx.data console to run SQL in the browser against an associated engine. It's the fastest path from access granted to first result, with no driver or client install. Keep Infrastructure Manager for engine and topology administration, not query writing.
Full Explanation
The correct choice is the query workspace in the watsonx.data console, which runs SQL against an associated engine in the browser. It lets a user select an engine, browse the catalogs associated with it, and run SQL directly in the browser. For ad hoc exploration by someone who already has access, it removes every client-side prerequisite.
The Infrastructure Manager option is incorrect because Infrastructure Manager manages engines, services, catalogs, buckets, and the associations between them. It is where you see and change topology, not where you write queries.
The locally installed Presto CLI option is incorrect because the query workspace is available to users according to their assigned access, not restricted to administrators. A CLI is a perfectly valid client, but it is an unnecessary prerequisite here.
The object storage console option is incorrect because previewing objects in a bucket shows files, not tables. It bypasses the catalog that defines the table and the access controls that govern it, and it will not answer an analytical question.
For the exam, keep the consoles distinct: query workspace for SQL, query history for what ran, Infrastructure Manager for what is connected, Data manager for the data assets themselves.