
Answer-first summary for fast verification
Answer: If using the stored procedure to execute multiple SQL statements, it's best to test run the stored procedure separately to size the compute resource first
The question asks how to determine the appropriate virtual warehouse size for a task. Option C is correct because when using stored procedures that execute multiple SQL statements, testing the procedure separately allows you to observe resource consumption and performance characteristics, enabling proper warehouse sizing based on actual workload requirements. This approach provides empirical data for sizing decisions. Option A discusses task concurrency margins but doesn't address warehouse sizing determination. Option B is incorrect because querying stream content size doesn't directly correlate to warehouse sizing needs - stream size indicates data volume but not the computational complexity or resource requirements of the operations. Option D is incorrect because multi-cluster warehouses handle concurrency scaling for multiple users/queries, but they don't help determine the appropriate base warehouse size for a task's computational requirements.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
How can you determine the size of the virtual warehouse that is being used for a task?
A
Root task may be executed concurrently (i.e. multiple instances), it is recommended to leave some margins in the execution window to avoid missing instances of execution
B
Querying (SELECT) the size of the stream content would help determine the warehouse size. For example, if querying large stream content, use a larger warehouse size
C
If using the stored procedure to execute multiple SQL statements, it's best to test run the stored procedure separately to size the compute resource first
D
Since task infrastructure is based on running the task body on schedule, it's recommended to configure the virtual warehouse for automatic concurrency handling using Multi-cluster warehouse (MCW) to match the task schedule
No comments yet.