Consider the following Snowflake warehouse definition: 'CREATE OR REPLACE WAREHOUSE MY WAREHOUSE WITH WAREHOUSE SIZE = 'MEDIUM' WAREHOUSE TYPE = 'STANDARD' AUTO SUSPEND = 300 AUTO RESUME = TRUE MIN CL

Question

Options

• AThe warehouse will automatically suspend after 5 minutes of inactivity.
• BThe warehouse will always have at least one active cluster.
• CThe warehouse can scale up to a maximum of three clusters to handle concurrent queries.
• DThe warehouse is optimized for minimizing costs rather than maximizing performance when
• EThe 'WAREHOUSE_TYPE = 'STANDARD" setting is invalid and will cause an error.

• A
  80% (20)
• E
  20% (5)

Explanation

All four correct answers map directly to parameters in the DDL statement. AUTO_SUSPEND = 300 means the warehouse suspends after 300 seconds (5 minutes) of inactivity, confirming A. MIN_CLUSTER_COUNT = 1 guarantees at least one cluster is always running, confirming B. MAX_CLUSTER_COUNT = 3 allows Snowflake's multi-cluster feature to spin up additional clusters for concurrent load, confirming C. SCALING_POLICY = 'ECONOMY' tells Snowflake to maximize cluster utilization before adding new clusters - prioritizing cost savings over instant scale-out - confirming D.

E is wrong because WAREHOUSE_TYPE = 'STANDARD' is perfectly valid; the only other supported type is SNOWPARK_OPTIMIZED. Standard is simply the default general-purpose type and causes no error.

Memory tip: Map each parameter acronym to its effect - think ARMS: Auto_suspend (time in seconds ÷ 60 = minutes), Resume (auto or manual), Min/Max cluster counts (floor and ceiling of scale), Scaling policy (Economy = cost-first, Standard = performance-first). If a setting exists in Snowflake's docs, it's valid - wrong syntax or unsupported values cause errors, not recognized keywords.

No community discussion yet for this question.