
Answer-first summary for fast verification
Answer: STATEMENT_QUEUED_TIMEOUT_IN_SECONDS, MAX_CONCURRENCY_LEVEL
The question asks for two parameters that work together to prevent a virtual warehouse backlog of queued SQL statements. STATEMENT_QUEUED_TIMEOUT_IN_SECONDS (A) controls how long a statement waits in the queue before timing out, directly addressing queued statements. MAX_CONCURRENCY_LEVEL (D) limits the number of concurrent queries a warehouse can execute, preventing excessive queuing by capping simultaneous operations. Together, they manage both queue duration and execution capacity to avoid backlogs. The community discussion confirms this pairing with 100% consensus and references Snowflake documentation. Other options are unsuitable: STATEMENT_TIMEOUT_IN_SECONDS (B) handles query runtime, not queuing; DATA_RETENTION_TIME_IN_DAYS (C) and MAX_DATA_EXTENSION_TIME_IN_DAYS (E) relate to data retention, not warehouse performance.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Which two parameters can be configured to prevent a virtual warehouse from having a backlog of queued SQL statements?
A
STATEMENT_QUEUED_TIMEOUT_IN_SECONDS
B
STATEMENT_TIMEOUT_IN_SECONDS
C
DATA_RETENTION_TIME_IN_DAYS
D
MAX_CONCURRENCY_LEVEL
E
MAX_DATA_EXTENSION_TIME_IN_DAYS