A BI platform must connect to watsonx.data to run its scheduled reports. Which interface is intended for this?
Select an answer to reveal the explanation.
Short Explanation
BI tools speak JDBC and ODBC, so point the tool at the query engine using its published connection details. You authenticate, and governance applies to every scheduled query. File-based workarounds quietly lose that control.
Full Explanation
The correct choice is the JDBC or ODBC connection to a query engine, using the engine's published connection details. Query engines expose standard JDBC and ODBC endpoints, which is how BI platforms are designed to connect. Queries then run under the connecting identity, so access policy applies to scheduled reports exactly as it does to interactive users.
The direct connection to the catalog service is incorrect because the catalog serves metadata, not rows. It has no query execution capability.
The shared bucket mount is incorrect because reading files directly bypasses both the table abstraction and governance, and it requires storage credentials the BI platform should not hold.
The export job that writes CSV files to a network share is incorrect because scheduled CSV exports create ungoverned copies that go stale between runs and sit outside every policy that applied to the source.
For the exam, associate BI connectivity with JDBC and ODBC against an engine.