What are some of the characteristics of result set caches? (Choose three.)

What are some of the characteristics of result set caches? (Choose three.)
A . Time Travel queries can be executed against the result set cache.
B . Snowflake persists the data results for 24 hours.
C . Each time persisted results for a query are used, a 24-hour retention period is reset.
D . The data stored in the result cache will contribute to storage costs.
E . The retention period can be reset for a maximum of 31 days.
F . The result set cache is not shared between warehouses.

View Answer

Answer: B, C, E

Explanation:

Comprehensive and Detailed According to the SnowPro Advanced: Architect documents and learning resources, some of the characteristics of result set caches are:

Snowflake persists the data results for 24 hours. This means that the result set cache holds the results of every query executed in the past 24 hours, and can be reused if the same query is submitted again and the underlying data has not changed1.

Each time persisted results for a query are used, a 24-hour retention period is reset. This means that the result set cache extends the lifetime of the results every time they are reused, up to a maximum of 31 days from the date and time that the query was first executed1.

The retention period can be reset for a maximum of 31 days. This means that the result set cache will purge the results after 31 days, regardless of whether they are reused or not. After 31 days, the next time the query is submitted, a new result is generated and persisted1.

The other options are incorrect because they are not characteristics of result set caches. Option A is incorrect because Time Travel queries cannot be executed against the result set cache. Time Travel queries use the AS OF clause to access historical data that is stored in the storage layer, not the result set cache2. Option D is incorrect because the data stored in the result set cache does not contribute to storage costs. The result set cache is maintained by the service layer, and does not incur any additional charges1. Option F is incorrect because the result set cache is shared between warehouses. The result set cache is available across virtual warehouses, so query results returned to one user are available to any other user on the system who executes the same query, provided the underlying data has not changed1.

Reference: Using Persisted Query Results | Snowflake Documentation, Time Travel | Snowflake Documentation