Which SQL statement will require a virtual warehouse to run?

The correct answer is C. INSERT INTO TBL_EMPLOYEE(EMP_ID, EMP_NAME, EMP_SALARY, DEPT). In Snowflake, DDL statements (CREATE, ALTER, DROP) are pure metadata operations executed by Snowflake's cloud services layer and do NOT require a running virtual warehouse. SELECT COUNT(*) is a special case: Snowflake stores row counts in micro-partition metadata, so this…

Snowflake Cloud Data Platform Features and Architecture

Question

Options

ASELECT COUNT{*) FROM TBL_EMPLOYEE;
BALTER TABLE TBL_EMPLOYEE ADD COLUMN EMP_REGI0N VARCHAR(20);
CINSERT INTO TBL_EMPLOYEE(EMP_ID, EMP_NAME, EMP_SALARY, DEPT)
DCREATE OR REPLACE TABLE TBL_EMPLOYEE (

How the community answered

(19 responses)

B
5% (1)
C
84% (16)
D
11% (2)

Explanation

In Snowflake, DDL statements (CREATE, ALTER, DROP) are pure metadata operations executed by Snowflake's cloud services layer and do NOT require a running virtual warehouse. SELECT COUNT(*) is a special case: Snowflake stores row counts in micro-partition metadata, so this specific query can be answered from metadata without spinning up a warehouse. INSERT INTO, however, is a DML (Data Manipulation Language) statement that writes data and must be processed by a virtual warehouse - it always requires active compute resources.

Topics

#Virtual Warehouse#Compute Layer#DML#Snowflake Architecture

Community Discussion

No community discussion yet for this question.

Full COF-C02 Practice