COF-C03 Practice Question: Performance Optimization, Querying, and Transformation
A Snowflake analyst runs a query that aggregates sales by region over the last 30 days. The query takes 40 seconds on an X-Small warehouse. The analyst then reruns the exact same query 10 minutes later without any data changes. It completes in 1 second. Which Snowflake feature explains this behavior?
⚠ Common exam trap
Many candidates confuse Result Cache with Local Disk Cache, since both improve performance on repeated queries but only Result Cache stores the final result set.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Result Cache
The dramatic speedup on an identical query with unchanged data is the signature of Result Cache. Snowflake stores the result set in the Cloud Services layer, so a repeat query is served without engaging the virtual warehouse. Local disk and metadata caches accelerate data scanning and pruning but still require query execution, and auto-suspend does not cache results.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Warehouse Auto-Suspend
Why it's wrong here
Auto-Suspend stops the virtual warehouse after a period of inactivity to save credits. It does not cache query results and would actually increase latency due to warehouse resume time. Since the query returned in 1 second without a resume delay, auto-suspend is not the cause of the performance improvement.
- ✓
Result Cache
Why this is correct
Result Cache stores the output of a query in the Cloud Services layer for 24 hours (or until the underlying data changes). Since the same query text was rerun and micro-partitions had no changes, Snowflake returned the cached result set without re-executing the query on the virtual warehouse. This is why the second run completed in 1 second.
- ✗
Metadata Cache
Why it's wrong here
Metadata Cache stores statistics like MIN/MAX values and distinct counts for micro-partitions, which helps the optimizer prune partitions. It does not store complete query results. A query that performs aggregation and returns rows must still be executed on the warehouse, so metadata caching would not reduce runtime to 1 second.
- ✗
Local Disk Cache
Why it's wrong here
Local Disk Cache caches raw micro-partition data on the virtual warehouse's local SSD to speed up subsequent scans, but it does not store the final query result set. Even with a warm local disk cache, the warehouse would still need to re-execute the aggregation. Therefore it cannot explain a 40-second query completing in 1 second.
About these practice questions
Courseiva writes every COF-C03 question from scratch — 280 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Snowflake exam blueprint
This COF-C03 practice question is part of Courseiva's free Snowflake certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the COF-C03 exam.