A Snowflake multi-cluster warehouse is appropriate when workloads generate consistent query concurrency with occasional increases in demand.
The scenario indicates that two Small clusters are required for routine activity, with temporary increases to three or four clusters during busier periods.
Option B correctly establishes a baseline of two clusters and allows Snowflake to automatically increase capacity when concurrent query demand grows.
When query activity declines, additional clusters can be removed according to the warehouse's scaling policy. AUTO_SUSPEND and AUTO_RESUME provide additional controls to prevent unnecessary compute usage during periods of inactivity.
The ANALYST role requires only USAGE to execute queries, preserving least-privilege access without permitting warehouse configuration changes.
Option A is unsuitable because manual cluster management introduces unnecessary administrative responsibility. Moreover, MANAGE is not the applicable object-level privilege for the described warehouse operations.
Option C confuses warehouse size with independent cluster capacity. A single X-Large warehouse does not provide the same concurrency-scaling behavior as four independently managed Small clusters.
Option D introduces operational complexity and requires users to select warehouses manually.
Terminology warning: The original choices use MIN_CLUSTERS. The actual Snowflake configuration parameter is MIN_CLUSTER_COUNT. Option B is conceptually correct, but its wording should be corrected before publication.
Official Snowflake references: Multi-cluster Warehouses; CREATE WAREHOUSE; Access Control Privileges.
Submit