SOL-C01 · Question #153
You are responsible for managing a Snowflake environment where data is loaded from various external sources. You want to use Snowsight to quickly identify all tables within a specific database and…
The correct answer is B. Query the Snowflake Information Schema using the Snowsight SQL Worksheet to retrieve the E. Use the Snowsight Data > Databases navigation to select the database and schema. Then, use. Options B and E work together as the most efficient and accurate solution. Option B leverages the Snowsight SQL Worksheet to query INFORMATION_SCHEMA.LOAD_HISTORY (or SNOWFLAKE.ACCOUNT_USAGE.LOAD_HISTORY), which contains precise timestamps for when data was last loaded into…
Question
You are responsible for managing a Snowflake environment where data is loaded from various external sources. You want to use Snowsight to quickly identify all tables within a specific database and schema that have not been loaded in the last 7 days. Which of the following methods, or combination of methods, provides the most efficient and accurate way to achieve this using Snowsight features?
Options
- AUse the Snowsight Search functionality to search for tables within the database and schema.
- BQuery the Snowflake Information Schema using the Snowsight SQL Worksheet to retrieve the
- CUse the Snowsight Data > Databases navigation to select the database and schema. Filter the
- DExecute a 'SHOW TABLES' command in the Snowsight SQL Worksheet and manually inspect the
- EUse the Snowsight Data > Databases navigation to select the database and schema. Then, use
How the community answered
(28 responses)- A4% (1)
- B61% (17)
- C14% (4)
- D21% (6)
Explanation
Options B and E work together as the most efficient and accurate solution. Option B leverages the Snowsight SQL Worksheet to query INFORMATION_SCHEMA.LOAD_HISTORY (or SNOWFLAKE.ACCOUNT_USAGE.LOAD_HISTORY), which contains precise timestamps for when data was last loaded into each table - this is the only way to get an accurate, queryable load history filtered to a 7-day window. Option E uses Snowsight's Data > Databases navigation to scope the view to the specific database and schema, complementing the SQL query with visual context and easy table browsing within that scope.
Why the distractors fail:
- A - Snowsight Search finds objects by name/type but has no capability to filter by last load date.
- C - The Databases navigation UI does not expose a built-in filter for "last loaded" timestamps; you can browse but not filter on load activity.
- D -
SHOW TABLESreturns table metadata (creation time, row count, etc.) but does not include load history timestamps, and manually inspecting results is error-prone and unscalable.
Memory tip: Think "navigation + SQL" - Snowsight's GUI narrows your scope (database/schema), while an Information Schema query gives you the precise time-based data you can't get from clicking alone. Whenever an exam question asks about when data was loaded, LOAD_HISTORY is your anchor.
Topics
Community Discussion
No community discussion yet for this question.