Course contents

SnowPro Core COF-C03 Study GuidePart 2: Warehouses and performanceExam Focus: Part 2

Exam Focus: Part 2

Exam Focus · Part 2

Read the symptom first, then pick the cheapest fix that works: size, clusters, a pruning service or the SQL.

Know these cold

TopicRemember
Credit ratesX-Small (Gen1) = 1 credit/h, doubling per size. Per second, 60 s minimum
Scale up vs outSpilling or one heavy query: bigger size. Queuing: more clusters
Multi-clusterEnterprise. Maximized: min = max. Auto-scale: min < max. Clusters all one size
Max clusters10 in Snowsight. SQL: up to 300 (XS–M), 10 at 4XL+
Scaling policyAuto-scale only. Standard: start on queuing. Economy: needs 6 minutes of work
Resource monitorACCOUNTADMIN creates it. One per warehouse, plus one account-level
Monitor actionsSUSPEND lets running queries finish. SUSPEND_IMMEDIATE cancels them
BudgetSees serverless and AI spend too. No built-in suspend; a custom action can
Full scansClustering: wide range filters. SOS (Enterprise+): selective lookups
QASEnterprise, per warehouse, for outlier scans. On by default for new standard warehouses

Traps

  • Myth Resizing cancels running queries.Fact They finish on the old size.
  • Myth A bigger warehouse fixes an exploding join.Fact It's a missing join condition. Fix the SQL.
  • Myth A resource monitor can cap Snowpipe or clustering spend.Fact Monitors see warehouse credits only.
  • Myth QAS scale factor 0 turns acceleration off.Fact 0 means no upper bound.
Before you turn the page
  • Recite the credit ladder from X-Small to 4X-Large.
  • Give the fix for each symptom: spilling, full scan, exploding join, queuing.
  • Say what SUSPEND and SUSPEND_IMMEDIATE do to running queries.