SnowPro Core (COF-C03) · Free practice question 3 of 15
Multi-cluster warehouses for concurrency
A team complains that their analytics dashboard is slow during business hours when many analysts hit it simultaneously, but it is fast off-hours. The warehouse is already an X-Large and a single query runs quickly when there is no other load. Which configuration change directly addresses concurrency contention?
- A.Increase the warehouse size to 2X-Large.
- B.Enable multi-cluster warehouse with auto-scale and a max cluster count greater than 1.
- C.Add a clustering key on the dashboard's main fact table.
- D.Increase the auto-suspend timer so the warehouse stays warm.
Show answer and explanation
Correct answer: B. Enable multi-cluster warehouse with auto-scale and a max cluster count greater than 1.
Why: The symptom is concurrency contention — many simultaneous queries during business hours — which multi-cluster warehouses solve by spinning up additional clusters of the same size as demand grows. Scaling up improves individual query speed but doesn't increase concurrent capacity. Clustering keys improve pruning, not concurrency. Auto-suspend timing affects warmup latency, not capacity.
More free SnowPro Core (COF-C03) questions
- Micro-partition immutability
- SECURITYADMIN for user and role management
- Snowflake edition for extended Time Travel
- Recovering a truncated table with Time Travel
- Types of internal stages
- File sizing for COPY INTO
- Query result cache
- Reader accounts for non-Snowflake consumers
- LATERAL FLATTEN on VARIANT arrays
- Streams and tasks for change data capture
- Clustering keys for partition pruning
- Network policies for IP allowlisting
- Zero-copy cloning for QA environments
- Snowpipe auto-ingest for low latency