For a multi-cluster warehouse, auto-suspend only occurs when the minimum number of clusters is running and there is no activity for the specified period of time.

• A. Auto-suspend occurs regardless of cluster activity
• B. Auto-suspend occurs only when there is activity
• C. Auto-suspend occurs only when the minimum number of clusters is not running
• D. Auto-suspend occurs only when the minimum number of clusters is running and there is no activity for the specified period of time

Answer: (D)

Auto-suspend in a multi-cluster warehouse uses two gating conditions: at least the configured minimum number of clusters must be running, and there must be no activity for the specified idle period. When the workload becomes idle and the cluster count is at or above the minimum, the system can suspend the extra clusters (leaving the minimum running) to save resources. If there is any activity, the idle timer resets and suspend won’t happen. If the number of running clusters is below the minimum, auto-suspend can’t occur because the system will scale up to meet the minimum first. So auto-suspend happens only when the minimum number of clusters is running and there has been no activity for the defined idle period. The other statements don’t fit because they ignore either the activity condition or the minimum-cluster constraint.