New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Snowflake ADA-C01 Exam - Topic 2 Question 30 Discussion

Actual exam question for Snowflake's ADA-C01 exam
Question #: 30
Topic #: 2
[All ADA-C01 Questions]

A Snowflake Administrator wants to create a virtual warehouse that supports several dashboards, issuing various queries on the same database.

For this warehouse, why should the Administrator consider setting AUTO_SUSPEND to 0 or NULL?

Show Suggested Answer Hide Answer
Suggested Answer: B

According to the Snowflake documentation1, a transient table is a type of table that does not support Time Travel or Fail-safe, which means that it does not incur any storage costs for maintaining historical versions of the data or backups for disaster recovery. A transient table can be dropped at any time, and the data is not recoverable. A transient table can also have a retention time of 0 days, which means that the data is deleted immediately after the table is dropped or truncated. Therefore, creating the staging table as a transient table with a retention time of 0 days can minimize the storage costs and maximize the performance, as the data is only loaded and transformed once, and then deleted after the production tables are populated. Option A is incorrect because creating the staging table as an external table, which references data files stored in a cloud storage location, can incur additional costs and complexity for data transfer and synchronization, and may not provide the best performance for data loading and transformation. Option C is incorrect because creating the staging table as a temporary table, which is automatically dropped when the session ends or the user logs out, can cause data loss or inconsistency if the session is interrupted or terminated before the production tables are populated. Option D is incorrect because creating the staging table as a permanent table, which supports Time Travel and Fail-safe, can incur additional storage costs for maintaining historical versions of the data and backups for disaster recovery, and may not provide the best performance for data loading and transformation.


Contribute your Thoughts:

0/2000 characters
Avery
3 months ago
Wait, are we sure AUTO_SUSPEND should be 0? Sounds risky!
upvoted 0 times
...
Beth
3 months ago
Totally agree with C, it really helps with similar queries!
upvoted 0 times
...
Annette
3 months ago
Isn't running it all the time gonna cost more in the long run?
upvoted 0 times
...
Raina
4 months ago
I think option C makes the most sense here.
upvoted 0 times
...
Celeste
4 months ago
Keeping the data cache warm is key for performance!
upvoted 0 times
...
Gerry
4 months ago
I think it’s definitely about keeping the cache warm, especially for repeated queries. I’d probably go with option D based on what we discussed in class.
upvoted 0 times
...
Mi
4 months ago
I feel like the main reason for not suspending the warehouse is to avoid costs from starting it up again, but I can't recall if that's the best answer here.
upvoted 0 times
...
Noemi
4 months ago
I remember a practice question where keeping the warehouse running was linked to performance, so I might lean towards option C or D.
upvoted 0 times
...
Johnathon
5 months ago
I think setting AUTO_SUSPEND to 0 helps with performance, but I'm not sure if it's specifically about the data cache or query result cache.
upvoted 0 times
...
Nada
5 months ago
I'm pretty confident on this one. Setting AUTO_SUSPEND to 0 or NULL means the warehouse won't automatically suspend, which will prevent the performance hit of having to warm up the cache for each new query. That'll be important for supporting those dashboards that are running lots of different queries. I'd go with option A as the best answer.
upvoted 0 times
...
Han
5 months ago
Okay, I've got a strategy for this. If I set AUTO_SUSPEND to 0 or NULL, that means the warehouse won't automatically suspend, right? So that should help keep the data cache and query result cache warm, which will improve performance for those repeated dashboard queries. And it'll save on the costs of constantly suspending and resuming the warehouse. I think option C is the way to go here.
upvoted 0 times
...
Carla
5 months ago
Hmm, I'm a bit unsure about this one. I know AUTO_SUSPEND has to do with automatically suspending the warehouse, but I'm not totally clear on the implications of setting it to 0 or NULL. I'll need to review the Snowflake documentation to make sure I understand the tradeoffs.
upvoted 0 times
...
Reita
5 months ago
This seems like a pretty straightforward question about Snowflake warehouse configuration. I think the key is understanding how AUTO_SUSPEND works and how it impacts performance and costs.
upvoted 0 times
...
Lawana
10 months ago
Decisions, decisions. I'm leaning towards C, but B made me chuckle. 'Running the warehouse as little as possible' - that's one way to save costs, I guess!
upvoted 0 times
Shay
9 months ago
C: A) To save costs on warehouse shutdowns and startups for different queries
upvoted 0 times
...
Tracie
9 months ago
B: C) To keep the data cache warm to support good performance of similar queries
upvoted 0 times
...
Dorcas
10 months ago
A: A) To save costs on warehouse shutdowns and startups for different queries
upvoted 0 times
...
...
Susana
10 months ago
Ah, I see what they're going for. A is a tempting choice, but I think C is the way to go. Gotta keep that data cache toasty!
upvoted 0 times
Tula
8 months ago
That's true, but keeping the data cache warm can also support good performance of similar queries.
upvoted 0 times
...
Eloisa
8 months ago
But wouldn't setting AUTO_SUSPEND to 0 or NULL save costs on warehouse shutdowns and startups?
upvoted 0 times
...
Willodean
9 months ago
Yeah, keeping the data cache warm is important for good performance.
upvoted 0 times
...
Kathryn
10 months ago
I think C is the way to go. Gotta keep that data cache toasty!
upvoted 0 times
...
...
Kris
11 months ago
I'm going with D. The query result cache is crucial for repeated queries, and keeping it warm can really boost performance.
upvoted 0 times
Nana
9 months ago
User 2: Yeah, I agree. It can really help boost performance.
upvoted 0 times
...
Janey
10 months ago
User 1: I think D is the best option. Keeping the query result cache warm is important for repeated queries.
upvoted 0 times
...
...
Adolph
11 months ago
Hmm, C seems like the best option here. Keeping the data cache warm for similar queries makes a lot of sense to me.
upvoted 0 times
Rose
9 months ago
I think both C and D are important for optimizing performance in this scenario.
upvoted 0 times
...
Lashon
9 months ago
That's true, having the query result cache warm would also improve performance.
upvoted 0 times
...
Carlee
9 months ago
But wouldn't D also be important for repeated queries?
upvoted 0 times
...
Lovetta
10 months ago
I agree, keeping the data cache warm would definitely help with performance.
upvoted 0 times
...
...
Romana
11 months ago
But wouldn't setting AUTO_SUSPEND to 0 or NULL also help in keeping the data cache warm for good performance of similar queries?
upvoted 0 times
...
Germaine
11 months ago
I agree with Mickie. Running the warehouse as little as possible can definitely help in saving costs.
upvoted 0 times
...
Mickie
11 months ago
I think the Administrator should consider setting AUTO_SUSPEND to 0 or NULL to save costs on warehouse shutdowns and startups for different queries.
upvoted 0 times
...

Save Cancel