Study SnowPro COF-C02 Query Profile: key concepts, common traps, and exam decision cues.
On this page
This lesson matters because strong COF-C02 answers usually start with evidence. Query profile exists so you can understand whether the slowdown is in scan volume, joins, remote I/O, or some other execution behavior before changing warehouses blindly.
Diagnosis chooser
If the question is mostly about…
Strongest first tool
understanding where time is going
query profile
comparing warehouse settings
warehouse configuration
reducing scan work
pruning and table design
What query profile is for
If you need to know…
Query profile helps with…
which step is consuming time
execution-stage evidence
whether the problem is scan-heavy or join-heavy
bottleneck localization
whether “make the warehouse bigger” is justified
evidence before resizing
It is not a magical auto-fix tool. It is the place you look before choosing the fix.
Decision order that usually wins
Start with evidence rather than warehouse resizing.
Use query profile to classify the bottleneck first.
If the evidence is scan-heavy, think pruning and query shape.
If the evidence points elsewhere, follow that lane before tuning compute.
Only resize after the execution evidence justifies it.
Common traps
Trap
Better rule
resizing first and reading later
read the evidence before changing compute
assuming all slowness is warehouse size
some issues are scan, join, or layout problems
using cost language to answer a pure diagnosis question
first locate the actual bottleneck
Scenario triage
Scenario clue
Stronger answer shape
“which part of the query is slow?”
query profile
“how can we tell whether the bottleneck is scan or join behavior?”