SnowPro Associate: Platform Question 260
Single answer● Use Snowsight to identify particular tablesA data engineer is asked to find a table named SALES_2024 in a Snowflake account, but they do not know which database or schema contains it. They have access to Snowsight and want the fastest way to identify the table location without writing SQL. Which action should they take in Snowsight?
- A
Use Snowsight's global search to search for SALES_2024 and review the returned database and schema location
- B
Open Worksheets and run USE DATABASE SALES_2024 to have Snowsight navigate to the table automatically
- C
Go to Admin > Warehouses and search for SALES_2024 because tables are indexed by the warehouse that last queried them
- D
Open Data > Databases and manually expand every database and schema until the table is found
Show answer and explanation
Correct answer: A
Explanation
This question tests practical navigation in Snowsight. When a user needs to identify a specific table and does not know its database or schema, the most efficient approach is to use Snowsight's search experience rather than manually browsing the object tree or issuing context-setting SQL commands. Snowflake documentation and Snowsight best practices emphasize using the UI to explore and search accessible database objects efficiently. Warehouses are unrelated to object discovery because they provide compute, while database, schema, and table metadata are part of Snowflake's catalog. Therefore, using Snowsight global search is the correct applied solution.
- A. Correct.
Correct. In Snowsight, the global search capability can be used to locate objects such as tables by name across accessible objects in the account. This is the most efficient UI-based method when the database and schema are unknown and the user wants to avoid writing SQL.
- B. Incorrect.
Incorrect. USE DATABASE is a SQL command for setting database context, not for locating a table by object name. SALES_2024 is a table name in this scenario, not a database name, so this command would not help identify the table's location.
- C. Incorrect.
Incorrect. Warehouses are compute resources and do not serve as a navigation index for locating table objects in Snowsight. A common misconception is that because warehouses execute queries, they also organize or own table metadata. Table metadata is stored in the catalog, not under warehouse administration.
- D. Incorrect.
Incorrect. A user could manually browse Data > Databases, but this is inefficient and does not represent the best way to identify a specific table when its location is unknown. The question asks for the fastest action in Snowsight without writing SQL, making global search the better choice.