An application team requests a connection to watsonx.data for a reporting tool. The platform team must supply the connection details. Which set is required for a JDBC connection to a Presto engine?
Select an answer to reveal the explanation.
Short Explanation
You need a JDBC connection to reach the Presto engine, so you give it the engine's host and port, the catalog and schema to query, and credentials the platform recognises. Handing over storage keys instead is a different connection entirely—one that skips the engine and the governance with it.
Full Explanation
The correct answer is the set that gives the engine's host and port, the catalog and schema to query, and credentials the platform recognises. A client connects to a Presto engine at a network address, then names the catalog and schema that scope its queries, and authenticates with platform credentials so access policies apply. Those are the details the platform team needs to supply.
The object storage endpoint, bucket name and storage access key are incorrect because those are storage credentials, not engine credentials. Giving them out would let the tool read files directly from the bucket, bypassing the catalog and every policy attached to it - a governance failure rather than a connection.
The catalog's internal identifier and the administrator's console session token are incorrect on two counts. A console session token is a short-lived, personal artefact that should never be shared with an application, and the catalog's internal identifier is not what a JDBC URL takes.
The answer that says only the engine name is needed, because the platform resolves everything else from the user's role, is incorrect because a connection has to reach a network endpoint before any role can be evaluated. Roles determine what the connection may see once established; they do not establish it.
For the exam, be able to list what a client needs to consume lakehouse data: engine endpoint, catalog and schema, and platform credentials.