SnowPro Associate: Platform Question 55
Single answerObject browsersA data engineer is using Snowsight to validate whether a newly created table and its columns are visible to her role before sharing screenshots with an analyst team. She wants to inspect objects interactively without writing SQL and also review table details such as columns and definitions. Which Snowsight feature should she use?
- A
Use the Data object browser to navigate databases, schemas, and tables, then open the table to inspect its columns and details
- B
Use the Query History page, because it lists all objects available to the current role and shows column definitions for each table
- C
Use the Warehouses page, because warehouse metadata includes the tables and columns accessible through that warehouse
- D
Use the Users & Roles page, because it provides an interactive browser of database objects and table definitions for the selected role
Show answer and explanation
Correct answer: A
Explanation
This question tests practical understanding of object browsers in Snowsight. For browsing databases, schemas, tables, views, and inspecting object details without writing SQL, Snowflake provides the Data object browser in Snowsight. This is the correct tool for interactively validating whether objects are visible to the current role and for reviewing metadata such as table columns. By contrast, Query History is for reviewing executed SQL, Warehouses is for compute resource management, and Users & Roles is for security administration rather than object exploration. Snowflake documentation for Snowsight and database object navigation emphasizes using the Data page to browse and inspect objects available to the active role.
- A. Correct.
Correct. In Snowsight, the Data object browser is the interactive interface for browsing databases, schemas, and objects such as tables and views. A user can expand the hierarchy and open a table to inspect details including columns, making it the right choice when the goal is to validate object visibility and inspect metadata without writing SQL.
- B. Incorrect.
Incorrect. Query History shows previously executed statements and their results or status, not a full interactive browser of all available database objects. While SQL run from Query History might reference objects, Query History is not designed to browse table structures or confirm object visibility comprehensively.
- C. Incorrect.
Incorrect. The Warehouses page is used to view and manage virtual warehouses and their state, size, and activity. Warehouses provide compute resources; they do not contain object metadata such as table and column definitions. This distractor reflects the common misconception that compute context determines object browsing capabilities.
- D. Incorrect.
Incorrect. The Users & Roles area is used to review and manage principals and privileges, but it is not the primary object browser for navigating database objects like tables and columns. Although role selection affects what objects are visible, the actual interactive browsing of those objects is done from the Data page.