Study COF-C03 Interfaces, Warehouses, and Modern Platform Features: key concepts, common traps, and exam decision cues.
After you understand Snowflake’s core layers, the next job is to keep interfaces, object hierarchy, warehouses, and newer platform features in separate buckets. Many wrong answers sound plausible only because they mix those roles together.
Snowsight: Snowflake’s web UI for worksheets, administration, monitoring, and other interactive platform tasks.
| Thing | Best mental bucket | Why the exam cares |
|---|---|---|
| Snowsight | interface | how users interact with Snowflake through the web UI |
| connector or driver | client connectivity | how applications and tools connect to Snowflake |
| database / schema / object | organization boundary | where tables, views, stages, and other objects live |
| virtual warehouse | compute boundary | where query and load compute is consumed |
The key distinction is that a warehouse is not part of the data-object hierarchy. A warehouse powers work. Databases, schemas, and objects organize and protect data.
| If the requirement is… | Better first thought |
|---|---|
| more compute-heavy work | larger warehouse or more compute |
| intermittent workload with cost discipline | auto-suspend and auto-resume |
| more concurrency | warehouse concurrency strategy or multi-cluster behavior |
| data access scope or privilege issue | not a warehouse problem; think roles and objects instead |
| Feature | Purpose-level meaning |
|---|---|
| notebook | interactive development and analysis surface inside Snowflake |
| Cortex | built-in AI capability family inside the Snowflake platform |
| Apache Iceberg table | open table-format interoperability concept relevant to current Snowflake data-platform awareness |
On COF-C03, these terms are more likely to appear as feature-awareness checks than as deep implementation questions. The exam usually wants you to recognize what problem family the feature belongs to.
COF-C03 often tests whether you can keep Snowflake’s surfaces in separate buckets. Warehouses power work, objects organize data, and interfaces are how people or tools reach the platform.
| Scenario | Better first move |
|---|---|
| question is about where a table lives | think database and schema hierarchy |
| question is about query power or concurrency | think warehouse |
| question is about interactive development in the UI | think notebook or Snowsight surface |
| modern feature term appears without deep technical detail | classify the feature family first |
| Trap | Better rule |
|---|---|
| choosing a warehouse answer for an object-hierarchy question | warehouse is compute, not organization |
| treating notebooks as the same thing as storage or governance | notebook is a work surface |
| assuming Iceberg is just another cache or share feature | Iceberg is about table-format interoperability |