A team is preparing a production rollout and needs to avoid a design mistake. Which approach best demonstrates API access in a IBM Certified watsonx Data Lakehouse Engineer environment?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Here's the deal: web scraping the UI or stealing session cookies isn't integration — it's a hack that will break the next time IBM pushes an update. Think of the watsonx.data APIs like a proper loading dock at a warehouse: applications that need programmatic access should use the officially supported REST APIs and clients, not sneak in through a side window. Use the front door.
Full explanation below image
Full Explanation
IBM watsonx.data exposes REST APIs and client SDKs for programmatic access to resources including catalogs, engines, schemas, and queries. The correct answer — using supported APIs and clients when applications need programmatic access — reflects IBM's documented integration patterns and ensures stability, security, and supportability. Scraping the web UI as an integration strategy (Option A) produces brittle integrations that break whenever the UI is updated and provides no SLA guarantees from IBM. Sharing administrator cookies with applications (Option B) is a security vulnerability that bypasses authentication controls and would fail any security audit. Generating SQL by editing browser local storage (Option D) is nonsensical and would corrupt session state while providing no durable integration path. The certification expects candidates to know that production integrations with watsonx.data must go through supported, authenticated API surfaces — never through undocumented UI internals.