SnowPro Associate: Platform Question 262
Single answer● Use Snowsight to identify particular tablesA data engineer is using Snowsight to investigate storage costs in a production database. They need to quickly identify tables in the SALES schema that are likely driving the highest storage usage so they can review them with the team. Which action in Snowsight is the most appropriate for finding those particular tables?
- A
Open Data » Databases, navigate to the SALES schema, and use the tables list in Snowsight to sort or inspect table details such as size/storage-related metadata
- B
Open Worksheets and run USE SCHEMA SALES; SHOW COLUMNS IN SCHEMA SALES; to identify the largest tables
- C
Open Activity » Query History and filter for INSERT statements against SALES to determine which tables currently consume the most storage
- D
Open Admin » Warehouses and review warehouse credit consumption to identify which SALES tables use the most database storage
Show answer and explanation
Correct answer: A
Explanation
This question tests whether the candidate knows how to use Snowsight for object discovery and inspection rather than relying on unrelated UI areas or incorrect SQL commands. To identify particular tables in a schema, especially when investigating storage, the most appropriate Snowsight workflow is to navigate through Data, select the database and schema, and review the table list and table details. In Snowflake best practices, Snowsight is used to browse database objects and inspect metadata visually, while Activity and Warehouses are intended for query monitoring and compute administration. The key distinction is understanding which Snowsight area is designed for finding and examining tables versus monitoring workloads or warehouses.
- A. Correct.
Correct. In Snowsight, the Data area is the appropriate place to browse databases, schemas, and tables. A user can navigate to the relevant schema and inspect the table list and table-level details to identify particular tables, including those relevant for storage review. This aligns with the practical use of Snowsight as a UI for object discovery and inspection.
- B. Incorrect.
Incorrect. SHOW COLUMNS lists column definitions, not which tables are largest. While SQL can be used in a worksheet to inspect metadata, this specific command does not help identify high-storage tables. A candidate might choose this because it mentions the correct schema and a metadata command, but it targets columns rather than table size.
- C. Incorrect.
Incorrect. Query History shows executed queries, not authoritative table storage metrics. Frequent INSERT activity does not necessarily mean a table is currently the largest. Someone might pick this option because recent data loads can contribute to growth, but query activity is not the correct way in Snowsight to identify particular tables by storage footprint.
- D. Incorrect.
Incorrect. Warehouse credit consumption relates to compute usage, not storage used by specific tables. Reviewing warehouses can help analyze performance or cost from compute, but it does not identify which tables in a schema are consuming the most storage. This distractor reflects a common confusion between compute costs and storage costs in Snowflake.