Exam SnowPro Core topic 1 question 762 discussion

D correct - Snowflake provides some object-level parameters that can be set to help control query processing and concurrency: STATEMENT_QUEUED_TIMEOUT_IN_SECONDS STATEMENT_TIMEOUT_IN_SECONDS https://docs.snowflake.com/en/user-guide/warehouses-overview

The information about the object-level parameters that can be set to help control query processing and concurrency in Snowflake can be found in the Snowflake documentation. Specifically, the MAX_CONCURRENCY_LEVEL and STATEMENT_QUEUED_TIMEOUT_IN_SECONDS parameters are used to manage query processing and concurrency.

Query processing and concurrency¶ The number of queries that a warehouse can concurrently process is determined by the size and complexity of each query. As queries are submitted, the warehouse calculates and reserves the compute resources needed to process each query. If the warehouse does not have enough remaining resources to process a query, the query is queued, pending resources that become available as other running queries complete. Snowflake provides some object-level parameters that can be set to help control query processing and concurrency: STATEMENT_QUEUED_TIMEOUT_IN_SECONDS STATEMENT_TIMEOUT_IN_SECONDS

Snowflake provides some object-level parameters that can be set to help control query processing and concurrency: STATEMENT_QUEUED_TIMEOUT_IN_SECONDS STATEMENT_TIMEOUT_IN_SECONDS

Statements A and E are correct: https://docs.snowflake.com/en/sql-reference/parameters#statement-queued-timeout-in-seconds STATEMENT_QUEUED_TIMEOUT_IN_SECONDS Amount of time, in seconds, a SQL statement (query, DDL, DML, etc.) remains queued for a warehouse before it is canceled by the system. This parameter can be used in conjunction with the MAX_CONCURRENCY_LEVEL parameter to ensure a warehouse is never backlogged.

In my opinion ADE are correct. The question should be more specific. If I had to choose, I would choose AD A for increasing/decreasing number of concurrent queries D for increasing the processing time

MAX_CONCURRENCY_LEVEL parameter to limit the number of concurrent queries running in a warehouse. Amount of time, in seconds, after which a running SQL statement (query, DDL, DML, etc.) is canceled by the system. A,D

STATEMENT_TIMEOUT_IN_SECONDS: Amount of time, in seconds, after which a running SQL statement (query, DDL, DML, etc.) is canceled by the system. STATEMENT_QUEUED_TIMEOUT_IN_SECONDS: Amount of time, in seconds, a SQL statement (query, DDL, DML, etc.) remains queued for a warehouse before it is canceled by the system. This parameter can be used in conjunction with the MAX_CONCURRENCY_LEVEL parameter to ensure a warehouse is never backlogged.

correct