SOL-C01 · Question #102
You have a Snowflake virtual warehouse named 'ANALYTICS WH' that is used for complex data transformations. You need to ensure that the warehouse automatically suspends itself when it's idle to minimiz
The correct answer is D. Set 'AUTO SUSPEND = 300' and 'AUTO RESUME = TRUE on the warehouse. Create a. Option D is correct because AUTO_SUSPEND = 300 (5 minutes) strikes the right balance for complex data transformations - aggressive enough to save costs during idle periods, but not so short (like 60 seconds) that the warehouse repeatedly suspends mid-pipeline or during brief paus
Question
You have a Snowflake virtual warehouse named 'ANALYTICS WH' that is used for complex data transformations. You need to ensure that the warehouse automatically suspends itself when it's idle to minimize costs, but also want to ensure it can quickly resume when a query is submitted. You also want to scale up the warehouse size during peak business hours to handle increased query load. Which of the following actions should you take?
Options
- ASet 'AUTO SUSPEND = 60' and 'AUTO RESUME = TRUE on the warehouse. Schedule a task
- BSet 'AUTO SUSPEND = 3600' and 'AUTO RESUME = FALSE on the warehouse. Manually resize
- CSet 'AUTO SUSPEND = 60' and 'AUTO RESUME = TRUE on the warehouse. Use Resource
- DSet 'AUTO SUSPEND = 300' and 'AUTO RESUME = TRUE on the warehouse. Create a
- EConfigure a Resource Monitor with a predefined credit quota and assign it to the `ANALYTICS
How the community answered
(24 responses)- A4% (1)
- C13% (3)
- D79% (19)
- E4% (1)
Explanation
Option D is correct because AUTO_SUSPEND = 300 (5 minutes) strikes the right balance for complex data transformations - aggressive enough to save costs during idle periods, but not so short (like 60 seconds) that the warehouse repeatedly suspends mid-pipeline or during brief pauses between transformation steps. AUTO_RESUME = TRUE ensures queries automatically trigger a resume with no manual intervention, and creating a scheduled Task to resize the warehouse handles the peak-hours scaling requirement directly.
Why the distractors fail:
- A & C both use
AUTO_SUSPEND = 60, which is too aggressive for complex transformations - a 1-minute idle threshold risks constant suspend/resume churn that can delay jobs and increase overhead. - B sets
AUTO_RESUME = FALSE, meaning someone must manually resume the warehouse before queries can run - directly contradicting the "quickly resume" requirement - and 3600 seconds wastes an hour's worth of credits while idle. - E misapplies Resource Monitors, which track and alert on credit consumption but do not control suspend/resume behavior or warehouse sizing.
Memory tip: Think of the three knobs as a trio - 300s suspend (not too hot, not too cold), AUTO_RESUME = TRUE (never locked out), and a scheduled Task (your peak-hours alarm clock). If any knob is missing or misconfigured, the cost-vs-performance balance breaks.
Topics
Community Discussion
No community discussion yet for this question.