Which Snowflake warehouse size option will generally cost the least while still allowing for moderate query performance?
Think about how warehouse size affects compute credits used per hour.
Smaller warehouses use fewer compute credits per hour, so an X-Small warehouse costs less than larger sizes. It is suitable for moderate workloads that do not require high concurrency or very fast processing.
What happens to your Snowflake compute costs if you enable auto-suspend on your warehouse with a 5-minute timeout?
Consider what auto-suspend does to warehouse activity.
Auto-suspend automatically stops the warehouse after the specified idle time, so compute costs stop accruing after 5 minutes of no activity.
You want to share data with multiple external partners without duplicating data and while minimizing costs. Which Snowflake feature should you use?
Think about sharing data without duplication and extra storage costs.
Snowflake Secure Data Sharing allows sharing live data without copying or moving it, reducing storage and maintenance costs.
What is a likely cost consequence of using a warehouse size much larger than needed for your workload?
Consider how warehouse size relates to billing and usage.
Snowflake charges based on warehouse size and active time. Using a larger warehouse than needed wastes compute credits on unused capacity, increasing costs.
You want to reduce Snowflake storage costs by automatically removing old data that is no longer needed. Which approach is best?
Think about balancing data availability and storage cost.
Setting a short Time Travel retention period and enabling automatic purging removes old data efficiently, reducing storage costs while keeping recent data accessible.