After deploying watsonx.data, analysts can sign in but every one of them sees only an empty catalog list, while the administrator sees all catalogs. What is the most likely cause?
Select an answer to reveal the explanation.
Short Explanation
You've got authentication working because they can sign in, but authorization is missing because they see nothing. That gap is almost always the group-to-role mapping never being done—the federation got finished and the entitlement half got forgotten.
Full Explanation
The correct answer is the option stating that identity groups have not been mapped to platform roles and policies, so authenticated users hold no entitlements. Authentication and authorization are separate steps. Successful sign-in proves identity federation works; an empty catalog list for every non-administrative user indicates those identities carry no roles or policies. The administrator sees everything because that account holds broad rights independently of the mapping.
The option saying the engines have not been started is incorrect because stopped engines would affect the administrator identically, and the symptom is specific to non-administrative users.
The option saying object storage credentials are wrong is incorrect because storage credentials are held by the platform and used when reading data. Bad credentials produce query failures, not selective catalog invisibility.
The option saying the catalogs were created in a different region from the users' sign-in endpoint is incorrect because a regional mismatch would prevent access for everyone, again including the administrator.
For the exam, use the works for admin, empty for everyone else pattern as a direct pointer to missing role and policy assignment.