SnowPro Associate: Platform Question 56
Single answerObject browsersA data engineer is troubleshooting why a newly created table is not visible in Snowsight for another team member. Both users are looking in the database and schema object browser, but only the creator can see the table listed. The table was created successfully in a shared development database. What is the MOST likely reason the second user cannot see the table in the object browser?
- A
The second user’s current warehouse is suspended, so the object browser cannot display tables
- B
The second user’s active role does not have sufficient privileges on the schema or table, so the object browser does not list the object
- C
The table creator did not run ALTER TABLE ... REFRESH, so the metadata has not propagated to the object browser
- D
The second user must clone the schema locally before the object browser can display newly created tables
Show answer and explanation
Correct answer: B
Explanation
In Snowflake, object browsers such as those in Snowsight display databases, schemas, tables, and other objects based on the privileges available to the user’s active role. A common troubleshooting step is to verify that the user has the necessary grants, typically including USAGE on the database and schema, and appropriate privileges on the object itself. This aligns with Snowflake’s access control model and Snowsight behavior: object visibility is privilege-driven, not dependent on warehouse state, metadata propagation commands for standard tables, or cloning. Best practice is to confirm the active role in the session and review grants with SHOW GRANTS or applicable role and object privilege checks.
- A. Incorrect.
Incorrect. Warehouse state affects the ability to run compute operations, but browsing metadata in Snowsight is governed by privileges, not whether a virtual warehouse is running. A suspended warehouse would not normally prevent a user from seeing a table in the object browser.
- B. Correct.
Correct. The object browser in Snowsight only shows objects the active role is allowed to access. If the second user’s active role lacks required privileges, such as USAGE on the database and schema and appropriate privilege to access the table, the table may not appear in the browser. This is a common real-world issue when users switch roles or inherit different grants.
- C. Incorrect.
Incorrect. There is no requirement to run ALTER TABLE ... REFRESH for a standard Snowflake table to appear in the object browser. REFRESH is associated with external tables and metadata refresh scenarios, not standard table visibility in Snowsight.
- D. Incorrect.
Incorrect. Cloning a schema is unrelated to object browser visibility. Users do not need to clone objects for them to appear in Snowsight. Visibility is based on metadata access controlled by privileges and the currently active role.