The number of queries that a Virtual Warehouse can concurrently process is determined by (Choose two.):
The number of queries that a Virtual Warehouse can concurrently process is determined by (Choose two.):
The number of queries that a Virtual Warehouse can concurrently process is determined by the complexity of each query and the CONCURRENT_QUERY_LIMIT parameter set on the Snowflake account. The complexity of the queries directly affects the amount of compute resources needed to process them, thereby influencing the concurrency limit. Additionally, Snowflake allows configuring the maximum number of concurrent queries a warehouse can process using parameters like CONCURRENT_QUERY_LIMIT or MAX_CONCURRENCY_LEVEL.
Answer is correct. 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.
Answer: AC MAX_CONCURRENCY_LEVEL is set to 8 by default at account level and can be changed. In reality, we can have more than 8 concurrent queries as well. But it depends on the factors such as the complexity of the queries, their resource consumptions etc.
AC are correct
Only A and C is correct , B would also have been corrected if MAX_CONCURRENCY_LEVEL was given but here option is MAX_CONCURRENCY_LIMIT .
AB is the answer
What about parameter MAX_CONCURRENCY_LEVEL that defines the maximum number of parallel or concurrent statements a warehouse can execute? https://community.snowflake.com/s/article/Warehouse-Concurrency-and-Statement-Timeout-Parameters
https://docs.snowflake.com/en/user-guide/warehouses-overview.html#query-processing-and-concurrency AC are correct
AC is correct
I think it's A and B because "You can use the MAX_CONCURRENCY_LEVEL parameter to limit the number of concurrent queries running in a warehouse." and "The number of queries that a warehouse can concurrently process is determined by the size and complexity of each query. " here it seems the number of queries processed are determined by the query complexity and its size and not the data size.
https://docs.snowflake.com/en/user-guide/performance-query-warehouse-max-concurrency
I'd agree, but the parameter in that case would be MAX_CONCURRENCY_LEVEL, not CONCURRENT_QUERY_LIMIT
https://docs.snowflake.com/en/user-guide/warehouses-overview#query-processing-and-concurrency
https://docs.snowflake.com/en/user-guide/performance-query-warehouse-max-concurrency
I'd agree, but the parameter in that case would be MAX_CONCURRENCY_LEVEL, not CONCURRENT_QUERY_LIMIT
I'd agree, but the parameter in that case would be MAX_CONCURRENCY_LEVEL, not CONCURRENT_QUERY_LIMIT
I'd agree, but the parameter in that case would be MAX_CONCURRENCY_LEVEL, not CONCURRENT_QUERY_LIMIT
a & b are the answers