SnowPro Associate: Platform Question 261
Single answer● Use Snowsight to identify particular tablesA data engineer is using Snowsight to investigate storage growth in the SALES database. They know the table name contains the word "ORDER" but do not know which schema it is in. They want to quickly locate the exact table in the user interface without writing SQL. Which action in Snowsight will best help them identify the table?
- A
Open Data, browse to the SALES database, and use the object search/filter in the database objects pane to search for tables with names containing "ORDER" across schemas
- B
Open Activity and review query history until a statement referencing an ORDER table appears, then infer the schema from that query
- C
Open Warehouses and search warehouse names for "ORDER" to find the warehouse associated with the table
- D
Open Dashboards and search for a chart titled ORDER to identify the underlying table
Show answer and explanation
Correct answer: A
Explanation
The best answer is to use Snowsight's Data interface to browse database objects and apply search or filtering to find the relevant table. In Snowflake, databases contain schemas, and schemas contain tables and views. Snowsight is specifically designed to let users navigate these objects visually, making it the appropriate tool when the task is to identify a table by name without using SQL. Activity, Warehouses, and Dashboards serve different purposes: query monitoring, compute management, and visualization. Snowflake documentation and Snowsight best practices emphasize using the Data area for object discovery and inspection.
- A. Correct.
Correct. In Snowsight, the Data area is used to explore databases, schemas, tables, views, and related objects. When a user needs to identify a particular table by name pattern and does not know the schema, using the search or filter capability within the database object browser is the most direct UI-based method. This matches the requirement to find the table without writing SQL.
- B. Incorrect.
Incorrect. Query history in Activity can help investigate previously executed SQL, but it is an indirect and unreliable way to locate a table when the user simply knows part of the table name. It depends on someone having recently queried that table and does not provide a structured method to browse database objects.
- C. Incorrect.
Incorrect. Warehouses are compute resources, not containers for tables. Searching warehouse names will not help identify where a table is stored. This distractor reflects the common misconception that warehouses contain data objects rather than providing compute for processing workloads.
- D. Incorrect.
Incorrect. Dashboards are used for visualizations and monitoring, not for discovering database objects. Even if a dashboard happened to reference a table related to orders, this is not an appropriate or dependable way to identify the exact table and schema in Snowsight.