An application's queries against watsonx.data begin failing with permission errors after a governance review, though the application code has not changed. What is the most likely explanation?
Select an answer to reveal the explanation.
Short Explanation
When the code didn't change but permissions did, the governance review likely tightened policy and stripped access from the application's service identity. You should check the entitlements attached to that identity, because undocumented app permissions often break during reviews.
Full Explanation
Permission errors after a governance review, with no application code change, point directly to policy. The most likely explanation is that the review changed the policies attached to the application's service identity, removing access it previously held. Reviews commonly tighten broad grants, and a service identity that had inherited access through one of them loses it.
The JDBC driver version becoming incompatible as a result of the review is incorrect because a governance review does not alter driver versions, and a driver incompatibility presents as a connection or protocol error rather than a permission denial.
The engine being resized, with permissions re-derived from engine capacity, is incorrect because engine size has no relationship to entitlement. Capacity and permission are independent.
The tables being re-registered, which resets all queries to fail until the catalog is rebuilt, is incorrect because re-registration does not reset access, and there is no catalog rebuild step of that kind.
For the exam, read the error type as the clue: permission denied points to policy, not to infrastructure.