ADA-C01 Question 470
Single answerCreate resource monitorsA Snowflake administrator needs to control monthly credit consumption for a shared ETL warehouse used by several teams. The requirement is to receive an alert when usage reaches 75% of the monthly budget and to automatically prevent any new queries from starting once 100% of the budget is consumed, while allowing currently running statements to finish. Which configuration best meets this requirement?
- A
Create a resource monitor with a monthly frequency, set a NOTIFY trigger at 75 percent, and set a SUSPEND trigger at 100 percent. Assign the monitor to the ETL warehouse.
- B
Create a resource monitor with a monthly frequency, set a NOTIFY trigger at 75 percent, and set a SUSPEND_IMMEDIATE trigger at 100 percent. Assign the monitor to the ETL warehouse.
- C
Create a resource monitor with a monthly frequency, set a NOTIFY trigger at 75 percent, and set a SUSPEND trigger at 100 percent. Assign the monitor at the account level only.
- D
Create a warehouse parameter to notify at 75 percent of credits consumed and auto-resume off at 100 percent so that no new queries are accepted.
- E
Create a resource monitor with a daily frequency, set a NOTIFY trigger at 75 percent, and set a SUSPEND trigger at 100 percent. Assign the monitor to the ETL warehouse.
Show answer and explanation
Correct answer: A
Explanation
Resource monitors are the Snowflake mechanism used to control and observe credit consumption for warehouses or for the account. In this scenario, the administrator needs two behaviors: notification at 75% and stopping new work at 100% without terminating currently running queries. The correct action pairing is NOTIFY at 75% and SUSPEND at 100%. SUSPEND differs from SUSPEND_IMMEDIATE because SUSPEND lets running statements complete, while SUSPEND_IMMEDIATE halts warehouse activity immediately. Best practice is to scope the monitor to the intended warehouse when only one workload should be governed, and to choose a schedule frequency that matches the business budget period, such as MONTHLY for monthly credit controls. See Snowflake documentation for CREATE RESOURCE MONITOR, resource monitor trigger actions, and warehouse assignment behavior.
- A. Correct.
Correct. A resource monitor can be configured with thresholds and actions such as NOTIFY and SUSPEND. Using a monthly frequency aligns the monitor with the monthly budget. The SUSPEND action prevents the warehouse from starting new statements after the threshold is reached, but it allows currently running statements to complete, which matches the stated requirement. Assigning the monitor to the specific ETL warehouse scopes the control to that warehouse rather than to the entire account.
- B. Incorrect.
Incorrect. SUSPEND_IMMEDIATE suspends the warehouse immediately and attempts to stop running queries as soon as the threshold is hit. That does not meet the requirement to allow currently running statements to finish. This option is a common mistake when administrators confuse SUSPEND with SUSPEND_IMMEDIATE.
- C. Incorrect.
Incorrect. An account-level resource monitor applies to all warehouses in the account, not just the shared ETL warehouse. While the trigger actions themselves are valid, this would overreach and could disrupt unrelated workloads. The scenario specifically calls for controlling one shared ETL warehouse.
- D. Incorrect.
Incorrect. Snowflake does not provide a warehouse parameter that directly sends budget-threshold notifications or enforces credit-based query admission in the way described here. Credit consumption governance for warehouses is handled through resource monitors, not through generic warehouse parameters such as AUTO_RESUME or AUTO_SUSPEND settings.
- E. Incorrect.
Incorrect. A daily frequency would reset the monitor every day, which would not align with a monthly budget requirement. Although the trigger actions are otherwise reasonable, the monitor would track daily consumption cycles rather than the needed monthly budget period.