SnowPro Associate: Platform Question 22
Single answer● SnowsightA data analyst uses Snowsight to run several ad hoc queries against a shared development warehouse. The analyst wants to reduce wait times caused by manually selecting the warehouse each time and also wants future worksheets to automatically use the same warehouse, database, and schema context. Which action in Snowsight best meets this requirement?
- A
Set the worksheet context to the desired role, warehouse, database, and schema, and save the worksheet so future work continues with that context
- B
Create a result cache policy in Snowsight so all new worksheets automatically inherit the same warehouse and schema
- C
Pin the warehouse in Query History so Snowsight reuses it for all future worksheets across the account
- D
Use the Data loading page in Snowsight to define the default warehouse, database, and schema for all worksheets
Show answer and explanation
Correct answer: A
Explanation
This question tests practical use of Snowsight worksheet context. In Snowsight, users select the role, warehouse, database, and schema used to run SQL in a worksheet. Saving the worksheet preserves that context, which is useful for ongoing analysis in a consistent environment. Candidates should distinguish between worksheet/session context and unrelated features such as query history, data loading, or result caching. Snowflake documentation for Snowsight worksheets and SQL execution context describes selecting and using warehouse, database, schema, and role within the worksheet experience.
- A. Correct.
Correct. In Snowsight, worksheets have execution context such as role, warehouse, database, and schema. Setting that context in the worksheet and saving it is the practical way to preserve it for continued use. This aligns with how analysts commonly work in Snowsight when they want queries in that worksheet to run with a consistent context.
- B. Incorrect.
Incorrect. Snowflake provides query result caching, but there is no Snowsight feature called a result cache policy that sets default worksheet context. Result caching affects query performance and reuse of results, not which warehouse, database, or schema a worksheet uses by default.
- C. Incorrect.
Incorrect. Query History in Snowsight is for reviewing past queries and their details. It does not provide a mechanism to pin a warehouse and enforce that setting for future worksheets. This option reflects a plausible UI-based assumption, but it is not an actual Snowsight capability.
- D. Incorrect.
Incorrect. The Data loading area in Snowsight is used for loading data and related setup tasks, not for configuring default worksheet execution context across worksheets. Warehouse, database, schema, and role are managed in worksheet/session context, not through the loading interface.