Which practice best supports maintainable programmatic access to watsonx.data over time?
Select an answer to reveal the explanation.
Short Explanation
Use supported drivers and documented APIs with a separate service identity for each application and scoped permissions. It costs a little more up front, but you can revoke one integration without breaking the others and see from the audit log which one misbehaved.
Full Explanation
Using supported drivers and documented APIs with per-application service identities and scoped permissions is the best practice because documented interfaces are stable across releases, and per-application identities make access auditable, independently revocable, and limited to what each integration needs. The shared high-privilege account is incorrect because it makes every application as powerful as the most demanding one, makes the audit trail useless, and means credential rotation breaks all applications at once. The per-application replica approach is incorrect because replicated tables produce copies that drift, sit outside governance, and multiply the pipelines to maintain. Storing connection credentials in the application's source repository is incorrect because those credentials are exposed to everyone with repository access and persist in history after rotation; they belong in a secrets mechanism. For the exam, the maintainability answer combines supported interfaces with least-privilege per-application identities.