Examworthyexamworthy.comSnowPro Core Certification (COF-C03) cheat sheet
Snowflake
Free to share. Examworthy is not affiliated with or endorsed by Snowflake; COF-C03 and related marks belong to their respective owners.
At a glance
Format: Multiple choice and multiple select, at a Pearson VUE testing center or online proctored
Domain weight map
Heaviest first - spend your time hereHow this exam thinks
COF-C03 is a pick-the-right-feature exam: almost every question is a scenario with a stated constraint - cost, recovery window, latency, or least privilege - and the right answer is the cheaper, lower-overhead Snowflake feature built for exactly that need, not the heavier one that also works.
Spot the trap
Tempting wrong answers, and why they failCommon misconception
That a bigger warehouse needs its own copy of the data. Storage is centralised, so warehouses of any size read the same persisted data directly.
Snowflake AI Data Cloud Features and Architecture
Common misconception
That converting to a multi-cluster warehouse stops a query from spilling bytes, though extra clusters add concurrency, not memory, to the single cluster running the query.
Performance Optimization, Querying, and Transformation
Common misconception
That granting custom roles straight to ACCOUNTADMIN keeps account settings consistent. It concentrates privilege at the top and breaks least privilege.
Account Management and Data Governance
Common misconception
That ON_ERROR CONTINUE performs a dry run with no writes. It loads every good row and only skips bad ones; VALIDATION_MODE is the true dry run.
Data Loading, Unloading, and Connectivity
Common misconception
That sharing a table replicates a copy into the consumer account, who then pays for that storage.
Data Collaboration
Common misconception
That Standard's always-on encryption already includes customer-managed keys and private connectivity. Those first appear at Business Critical.
Snowflake AI Data Cloud Features and Architecture
Common misconception
That INFORMATION_SCHEMA.QUERY_HISTORY covers months of account-wide queries with no latency, when it is scoped and limited to about the last seven days.
Performance Optimization, Querying, and Transformation
Common misconception
That Snowflake grants privileges to users directly. Privileges attach to roles; a user only gains access by activating a role that holds them.
Account Management and Data Governance
Key terms
Exam-day rules
- Read the scenario for the constraint first. The stated need - lowest cost, the recovery window, the latency target, least privilege, one output file - is what picks the feature, so find it before you judge the options.
- When two features both work, pick the cheaper, lower-overhead one built for the job. A larger warehouse over a multi-cluster for a lone spilling query, a materialized view over a task-rebuilt summary table, zero-copy cloning over an actual copy.
- Diagnose performance from what Query Profile shows, not from a favourite fix. Bytes spilled to storage mean a memory shortfall, so scale the warehouse size up; a clustering key, more clusters, or the result cache do not address spilling.
- Default to least privilege on the role hierarchy. Grant custom object-creating roles under SYSADMIN, use SECURITYADMIN for grants and ORGADMIN for provider setup, and never reach for ACCOUNTADMIN just because it would also work.
- Split the policies by what the requirement controls. If it is about which rows appear, it is a row access policy; if it is about how a column value looks, it is a masking policy; join a mapping table when assignments change often so you never edit the policy.
Revision schedule
- Day 1Map the blueprint and book a date
- Week 1Build the architecture and feature-decision maps
- Weeks 1 to 2Go deep on architecture and performance
- Weeks 2 to 3Lock governance and the role hierarchy
- Week 3Cover loading, unloading, and collaboration