ARA-C01 Snowflake Architecture Practice Question
A Snowflake architect is designing a multi-cluster warehouse for a workload that experiences unpredictable spikes in concurrency. The architect wants to ensure that queries are not queued unnecessarily while minimizing credit consumption during periods of low demand. The warehouse is configured with a minimum cluster count of 1 and a maximum of 5. Which scaling policy should the architect choose to best meet these goals?
⚠ Common exam trap
It's easy for candidates to confuse the warehouse auto-suspend setting with the multi-cluster scaling policy, or assuming a policy called Maximized exists.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Standard scaling policy
The Standard scaling policy is designed to minimize queuing by promptly adding clusters when queries are waiting, and it scales down after inactivity to save credits. Economy scaling is more conservative and may allow queuing during rapid spikes. Auto-suspend is unrelated to cluster scaling, and Maximized is not a valid policy. Therefore, Standard best meets the requirement to handle unpredictable concurrency without excessive credit use.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Auto-suspend scaling policy
Why it's wrong here
Auto-suspend is a warehouse setting that controls how long a warehouse remains idle before suspending, not a scaling policy for multi-cluster warehouses. While it affects credit consumption, it does not govern how clusters scale in response to concurrency. This option confuses a warehouse property with a scaling policy and would not address the queuing behavior during spikes.
- ✗
Maximized scaling policy
Why it's wrong here
Snowflake does not offer a scaling policy called 'Maximized.' The available policies are Standard and Economy. Choosing a non-existent policy would not configure the warehouse correctly. The architect must select from the actual scaling policies to achieve the desired balance between responsiveness and cost.
- ✓
Standard scaling policy
Why this is correct
The Standard scaling policy starts additional clusters immediately when queries are queued, up to the maximum, and shuts them down after a period of inactivity (default 60 seconds). This minimizes queuing during sudden spikes and reduces credits during low demand by scaling down. It is designed for workloads that require high concurrency and can tolerate some credit usage for responsiveness, matching the scenario's need to avoid unnecessary queuing while controlling costs.
- ✗
Economy scaling policy
Why it's wrong here
Economy scaling favors keeping clusters running longer to avoid the overhead of starting new ones, which conserves credits during stable periods but can lead to queuing when demand spikes suddenly. It does not aggressively add clusters to handle unpredictable spikes, so queries may wait. This policy is better suited for workloads with gradual changes, not the unpredictable spikes described.
About these practice questions
Courseiva writes every ARA-C01 question from scratch — 209 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Snowflake exam blueprint
This ARA-C01 practice question is part of Courseiva's free Snowflake certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ARA-C01 exam.