Study SnowPro COF-C02 Layers and Warehouses: key concepts, common traps, and exam decision cues.
On this page
This lesson matters because many COF-C02 questions are simple once you classify the layer first. Storage holds the data, warehouses supply compute, and cloud services coordinate the platform. If those blur together, cost and performance questions become guesswork.
Layer chooser
If the question is mostly about…
Strongest first layer
where the data persists
storage
where queries, loads, and transforms run
virtual warehouse
metadata, auth, and coordination
cloud services
Read the requirement in the right order
Ask this first
Why it matters
is the question about where data lives, where work runs, or who coordinates the platform?
storage, compute, and cloud services are different lanes
is the answer changing capacity or changing data state?
resizing a warehouse is not a storage operation
is the stem really about feature availability or SLA level?
edition wording is often the clue
What the exam is really testing
If the scenario shows…
Strong reading
changing warehouse size
compute behavior is under test
concern about stored data growth
storage is under test
auth, metadata, or optimization language
cloud services awareness matters
edition wording
feature-availability awareness matters more than memorizing marketing names
Why editions matter
COF-C02 does not expect a pricing-pitch answer. It expects you to notice when the scenario depends on capability availability, service level, or advanced feature support. If the requirement hinges on what the account is allowed to use, the edition clue matters. If the question is only about a slow query, edition is usually a distraction.
Decision order that usually wins
Separate storage, compute, and cloud services first.
Ask whether the clue is about persistence, execution, or platform coordination.
Keep warehouse resize answers in the compute lane.
If the stem depends on capability availability or service level, check edition awareness.
Do not let edition language distract you from an ordinary compute or storage question.
Common traps
Trap
Better rule
assuming a larger warehouse changes stored data layout
warehouse changes affect compute, not where data lives
treating editions as pure pricing trivia
editions matter because some capabilities and SLAs differ
merging cloud services into the warehouse bucket
control-plane coordination is a separate layer
Scenario triage
Scenario clue
Stronger answer shape
“we need faster execution for the same query”
compute lane, usually warehouse behavior
“we need to understand metadata and authentication coordination”