Answer: Removing a column from the query SELECT list, Changing a column that is not in the cached query

The question asks which actions prevent leveraging the ResultSet cache, requiring selection of two correct options. Based on Snowflake documentation and community consensus: A (Removing a column from the query SELECT list) prevents cache use because it changes the query text, making it different from the cached version. E (Changing a column that is not in the cached query) also prevents cache use, as confirmed by multiple users who tested this scenario—even changes to columns not referenced in the query invalidate the cache due to underlying data modifications. Option C (Clustering of the data used by the query) is debated; while some argue it prevents cache use by altering micro-partitions, the prevailing view (with higher upvotes) is that clustering alone does not invalidate the cache unless it involves reclustering or consolidation, which isn't specified here. Option B (Stopping the virtual warehouse) is incorrect because the ResultSet cache is independent of warehouses. Option D (Executing RESULTS_SCAN()) is unrelated to cache prevention. Thus, A and E are the optimal choices, supported by testing and documentation insights.

Author: LeetQuiz Editorial Team