Snowflake Accounts and Virtual Warehouses
This domain (~15% of the SnowPro Core exam, roughly 15–16 scored questions out of ~100) tests whether you can administer an account and run compute economically. Expect heavy emphasis on: which edition unlocks which feature, warehouse sizing math and credit consumption, the difference between scaling up and scaling out, scaling-policy behavior, resource-monitor triggers and their exact scope, parameter hierarchy and defaults, the three cost categories (compute / storage / data transfer), and choosing the right metadata source (ACCOUNT_USAGE vs INFORMATION_SCHEMA vs ORGANIZATION_USAGE). Questions are overwhelmingly fact-recall and scenario-selection, not SQL syntax. Memorize the numbers.
Account-level objects: organizations, accounts, editions
An organization is the top-level container Snowflake assigns to a customer. It groups one or more accounts, each of which lives in exactly one cloud provider (AWS, Azure, GCP) and one region. Accounts in the same organization may sit in different clouds and regions.
Hierarchy and roles
| Level | Managed by role | Typical tasks |
|---|---|---|
| Organization | ORGADMIN | Create accounts, view org-wide usage, enable account replication/failover, view/change organization name, list accounts |
| Account | ACCOUNTADMIN | Create resource monitors, set account parameters, manage editions/billing views, top of role hierarchy |
| Security/users | SECURITYADMIN / USERADMIN | Roles, users, grants, network policies |
| Objects | SYSADMIN | Databases, schemas, warehouses |
ORGADMIN is not granted to users by default in every account — it exists in one account initially and can be granted by an existing ORGADMIN. ORGADMIN cannot see object data or grant itself data access; it is an administrative/billing role.
Account identifiers. Preferred form is orgname-account_name (URL: https://orgname-account_name.snowflakecomputing.com). The legacy form is the account locator plus region and cloud (e.g. xy12345.us-east-1.aws). Account names must be unique within the organization; account locators are assigned by Snowflake and cannot be changed.
Editions. Each account has exactly one edition. Editions are cumulative — each includes everything below it — and the credit price per compute-hour rises with edition (the credit consumption of a warehouse does not change; the dollar cost per credit does).
| Feature | Standard | Enterprise | Business Critical | VPS |
|---|---|---|---|---|
| Time Travel retention | 0–1 day | 0–90 days | 0–90 days | 0–90 days |
| Fail-safe (permanent tables) | 7 days | 7 days | 7 days | 7 days |
| Multi-cluster warehouses | ✗ | ✔ | ✔ | ✔ |
| Materialized views | ✗ | ✔ | ✔ | ✔ |
| Search Optimization Service | ✗ | ✔ | ✔ | ✔ |
| Query Acceleration Service | ✗ | ✔ | ✔ | ✔ |
| Dynamic Data Masking, row access policies, external tokenization, object tagging | ✗ | ✔ | ✔ | ✔ |
| ACCESS_HISTORY view | ✗ | ✔ | ✔ | ✔ |
| Periodic rekeying of encryption keys | ✗ | ✔ | ✔ | ✔ |
| Tri-Secret Secure / customer-managed key | ✗ | ✗ | ✔ | ✔ |
| PrivateLink / Private Service Connect | ✗ | ✗ | ✔ | ✔ |
| Failover/failback, client redirect, account replication | ✗ | ✗ | ✔ | ✔ |
| HIPAA / PCI DSS / HITRUST / ITAR support | ✗ | ✗ | ✔ | ✔ |
| Dedicated metadata store & isolated compute pool | ✗ | ✗ | ✗ | ✔ |
Available in all editions: automatic encryption at rest and in transit, ANSI SQL + ACID transactions, Secure Data Sharing, federated authentication/SSO, MFA, network policies, Snowsight, zero-copy cloning, semi-structured data support, database replication (read-only secondary), 24×7 Snowflake support.
Common traps
- Thinking multi-cluster warehouses are a Standard-edition feature. They require Enterprise or higher.
- Confusing replication (all editions, database-level, read-only secondary) with failover/failback and account-level replication (Business Critical+).
- Assuming 90-day Time Travel is a default. Default
DATA_RETENTION_TIME_IN_DAYSis 1 everywhere; 90 days is only the maximum on Enterprise+ and only for permanent objects. - Thinking VPS means "your own cloud account/VPC." VPS is a separate Snowflake deployment with its own metadata store; it is not a customer-hosted install.
- Believing an edition change is self-service downgrade. Upgrades/downgrades go through Snowflake (ORGADMIN can create accounts at a chosen edition).
- Mixing up ORGADMIN and ACCOUNTADMIN: only ORGADMIN creates accounts and reads ORGANIZATION_USAGE; only ACCOUNTADMIN creates resource monitors.
Worked scenario. A healthcare customer must store PHI, use customer-managed encryption keys, and connect from a private VPC without traversing the public internet. Which edition? → Business Critical. Enterprise gives masking and 90-day Time Travel but not Tri-Secret Secure, PrivateLink, or HIPAA support; VPS is valid but exceeds the requirement, and the exam expects the minimum edition that satisfies all stated needs.
Unlock with a paid plan
8 more sections (about 3,491 words) continue below. Every paid plan unlocks all COF-C03 study guides, the full question bank and mock exams, from $4.97/month.