COF-C03 Practice Question: Snowflake AI Data Cloud Features and Architecture
A data engineer runs a long-running aggregation query on a virtual warehouse. Mid-execution, the warehouse is resized from MEDIUM to LARGE. What happens to the query?
⚠ Common exam trap
The trap here is assuming that a resize immediately affects in-flight queries or that it interrupts them, when Snowflake defers the change until the warehouse is idle.
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
✓
The query continues running on the MEDIUM warehouse until completion, and the resize applies to subsequent queries.
When a warehouse is resized while queries are running, Snowflake postpones the change until the warehouse becomes idle. The running query continues on the original size and completes normally. The new size applies only to future queries after the warehouse restarts. This design avoids disrupting active workloads and ensures consistent execution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The query is cancelled and must be resubmitted manually after the resize completes.
Why it's wrong here
Snowflake never cancels a running query due to a warehouse resize. The resize operation itself waits for the warehouse to become idle. Manual resubmission is unnecessary and would defeat the purpose of the deferred resize behavior, which is designed to be transparent to users.
- ✗
The query fails with an error indicating the warehouse size changed during execution.
Why it's wrong here
A warehouse resize does not cause an active query to fail. Snowflake defers the resize until the warehouse is idle, so the query completes normally on the original size. There is no error condition triggered by an administrative resize request while queries are running.
- ✗
The query is paused, the warehouse resizes, and the query automatically resumes on the LARGE warehouse with full progress preserved.
Why it's wrong here
Snowflake does not checkpoint and resume a running query on a resized warehouse. Resizing occurs only when the warehouse has no active queries; otherwise, the change is queued. The scenario described would require an unsupported query migration mechanism, which Snowflake does not provide.
- ✓
The query continues running on the MEDIUM warehouse until completion, and the resize applies to subsequent queries.
Why this is correct
Snowflake does not migrate a running query to a differently sized warehouse. The resize takes effect only after the current query finishes and the warehouse restarts with the new size. This behavior prevents disruption and ensures query stability, though it means the in-flight query cannot benefit from the additional compute resources.
About these practice questions
This COF-C03 question is part of Courseiva's 280-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.