nerdexam
Snowflake

DEA-C02 · Question #3

A Data Engineer executes a complex query and wants to make use of Snowflake's query results caching capabilities to reuse the results. Which conditions must be met? (Choose three.)

The correct answer is D. The table structure contributing to the query result cannot have changed. E. The new query must have the same syntax as the previously executed query. F. The micro-partitions cannot have changed due to changes to other data in the table. Snowflake's result cache lives at the Cloud Services layer, completely independent of any virtual warehouse - making B wrong (no warehouse requirement) and invalidating A as well, since cached results expire after 24 hours, not 72. Option C is fabricated; USED_CACHED_RESULT is…

Performance Optimization

Question

A Data Engineer executes a complex query and wants to make use of Snowflake's query results caching capabilities to reuse the results. Which conditions must be met? (Choose three.)

Options

  • AThe results must be reused within 72 hours.
  • BThe query must be executed using the same virtual warehouse.
  • CThe USED_CACHED_RESULT parameter must be included in the query.
  • DThe table structure contributing to the query result cannot have changed.
  • EThe new query must have the same syntax as the previously executed query.
  • FThe micro-partitions cannot have changed due to changes to other data in the table.

How the community answered

(44 responses)
  • A
    5% (2)
  • B
    2% (1)
  • D
    93% (41)

Explanation

Snowflake's result cache lives at the Cloud Services layer, completely independent of any virtual warehouse - making B wrong (no warehouse requirement) and invalidating A as well, since cached results expire after 24 hours, not 72. Option C is fabricated; USED_CACHED_RESULT is not a real Snowflake parameter.

D, E, and F reflect the three genuine requirements: the query text must be byte-for-byte identical (E), the table structure (schema/metadata) must be unchanged (D), and the underlying micro-partitions must not have been altered by any DML - even changes to rows outside the query's result set can invalidate the cache because Snowflake tracks partition-level metadata, not row-level (F).

The reason F catches people off guard is the phrase "other data in the table" - Snowflake doesn't track which specific rows contributed to a result, so any write to the table (even rows you didn't query) can bust the cache.

Memory tip: Think "Same Query, Frozen Data, 24 Hours" - the query must be identical (E), the data/partitions untouched (D + F), and you must reuse within one day. If any of the three "S"s fail - Same text, Stable structure, Stable partitions - the cache is bypassed.

Topics

#Snowflake Caching#Query Performance#Result Cache#Micro-partitions

Community Discussion

No community discussion yet for this question.

Full DEA-C02 Practice