SnowPro Associate: Platform Question 54
Single answerObject browsersA data engineer is troubleshooting why a newly created table is not visible in Snowsight for another team member. Both users are connected to the same Snowflake account and warehouse, and the table was created successfully in a shared database and schema. The engineer wants to use Snowsight's object browser to confirm whether the issue is caused by object visibility or privileges. Which action is the MOST appropriate to validate this?
- A
Have the other team member switch to the same role used by the data engineer and refresh the Databases object browser to see whether the table appears under the expected database and schema.
- B
Ask the other team member to suspend and resume the warehouse, because the object browser only refreshes metadata after warehouse restart.
- C
Use the object browser to check whether Time Travel is enabled on the table, because tables without Time Travel do not appear in Snowsight.
- D
Drop and recreate the table with a fully qualified name, because the object browser only displays objects created with explicit database and schema names.
Show answer and explanation
Correct answer: A
Explanation
This question tests practical use of Snowsight's object browser to diagnose object visibility issues. In Snowflake, what a user sees in the object browser is determined by the currently active role and the privileges granted to that role. If an object exists but is not visible to another user, the first troubleshooting step is to verify role context and refresh the browser view. This aligns with Snowflake's access control model, where privileges on databases, schemas, and objects govern discoverability and access. Warehouses are not responsible for metadata visibility, and features such as Time Travel do not affect whether an object is listed in the browser. Best practice is to confirm the active role, confirm grants on the database/schema/object, and then use Snowsight's browser to validate visibility under that role.
- A. Correct.
Correct. In Snowsight, the object browser displays objects based on the privileges available to the active role. If one user can see a table and another cannot, a practical validation step is to have the second user switch to the same role, then refresh the Databases browser and navigate to the relevant database and schema. If the table becomes visible, the issue is role-based visibility or privilege-related rather than a problem with table creation.
- B. Incorrect.
Incorrect. Warehouse state does not control whether database objects appear in the object browser. Warehouses provide compute for query execution, but metadata visibility in Snowsight depends primarily on role-based access to account, database, schema, and object privileges.
- C. Incorrect.
Incorrect. Time Travel retention is unrelated to whether a table appears in the Snowsight object browser. A table can be visible regardless of its Time Travel settings, assuming the active role has the necessary privileges to view it.
- D. Incorrect.
Incorrect. A table does not need to be created with a fully qualified name to appear in the object browser. If the correct database and schema context were set at creation time, the object is created successfully and can be shown in the browser. Visibility problems are much more likely to be caused by privileges or role context.