Snowflake COF-C03: Snowflake accounts and virtual warehouses Practice Questions

AUTO_SUSPEND is the warehouse parameter that sets the idle-time threshold (in seconds) before the warehouse automatically suspends. STATEMENT_TIMEOUT_IN_SECONDS (option A) controls how long an individual statement is allowed to run before Snowflake cancels it, unrelated to idle suspension. AUTO_RESUME (option B) is a boolean controlling whether the warehouse restarts automatically on a new query, not a timing value. MAX_CONCURRENCY_LEVEL (option D) controls how many statements can execute concurrently on a warehouse cluster, not suspend timing.

Resource monitors in Snowflake can be scoped either to the account level (covering all warehouses, tracking overall account credit usage) or assigned to one or more specific virtual warehouses to cap their individual usage. They are not assigned to databases (option C, storage/credit usage for databases isn't governed by resource monitors) or to role grants (option D, which is an RBAC concept unrelated to credit monitoring).

Storage is billed separately from compute, based on the average monthly volume of compressed data held in Snowflake (including Time Travel and Fail-safe retained data), typically priced per terabyte. Virtual warehouse compute (option D) and serverless feature compute (option B, such as automatic clustering or Snowpipe) are billed in credits based on the compute consumed, not data volume. Cloud Services compute (option C) is also credit-based, covering metadata operations, query parsing/optimization, and similar, not raw stored volume.

The Economy scaling policy is more conservative about starting additional clusters — it waits for a higher confidence that the extra cluster will be fully utilized, favoring credit savings over immediately eliminating queuing. The Standard policy (option D) starts additional clusters more readily to minimize queuing at the cost of using more credits. Options A and C ('Balanced', 'Aggressive') are not Snowflake multi-cluster scaling policy names — Snowflake's two documented policies are Standard and Economy.

Dynamic data masking and row access policies are governance features introduced at Enterprise Edition. Standard Edition (option B) includes core warehouse/storage functionality but not these governance controls. Business Critical Edition (option C) and VPS (option D) are higher tiers that add stronger security/compliance features (like HIPAA support and dedicated infrastructure) and include everything Enterprise has, but Enterprise is the minimum edition where masking and row access policies become available, so they are not required.