Credit usage monitoring in Snowflake - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Querying total credits used by a Snowflake warehouse

What is the output of this query that sums the credits used by warehouse 'COMPUTE_WH' in the last 7 days?

Snowflake

SELECT SUM(CREDITS_USED) AS TOTAL_CREDITS
FROM SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY
WHERE WAREHOUSE_NAME = 'COMPUTE_WH'
AND START_TIME >= DATEADD(day, -7, CURRENT_TIMESTAMP());

A An empty result because START_TIME filter is invalid

B Multiple rows listing credits used per day for COMPUTE_WH in the last 7 days

C An error because WAREHOUSE_NAME is case sensitive and should be lowercase

D A single row with TOTAL_CREDITS showing the sum of credits used in the last 7 days for COMPUTE_WH

💡 Hint

Check the aggregation and filtering by warehouse and date range.

The query sums the CREDITS_USED column filtered by warehouse name and start time within the last 7 days, returning a single row with the total credits.

🧠 Conceptual

intermediate

Understanding Snowflake credit billing granularity

Which statement correctly describes how Snowflake bills credits for warehouses?

A Credits are billed per second with a minimum of 60 seconds per warehouse usage

B Credits are billed per query executed regardless of warehouse size

C Credits are billed per hour regardless of actual usage time

D Credits are billed only when data is stored, not when warehouses run

💡 Hint

Think about how Snowflake charges for compute time.

Snowflake bills warehouse credits per second with a minimum of 60 seconds per usage period, so short runs less than a minute still cost one minute of credits.

❓ Troubleshoot

advanced

Diagnosing missing credit usage data in ACCOUNT_USAGE

You run this query to check credit usage but get no rows returned: SELECT * FROM SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY WHERE START_TIME > CURRENT_DATE - 1; What is the most likely reason?

A The warehouse has not used any credits in the last day, so no data exists

B The query syntax is invalid because CURRENT_DATE cannot be used in WHERE clause

C The ACCOUNT_USAGE views have a latency of up to 45 minutes, so recent data may not appear yet

D The user running the query lacks privileges to see ACCOUNT_USAGE data

💡 Hint

Consider data availability delays in Snowflake's monitoring views.

Snowflake ACCOUNT_USAGE views have a delay of up to 45 minutes before data appears, so very recent usage may not be visible immediately.

🔀 Workflow

advanced

Automating credit usage alerts with Snowflake tasks

Which sequence correctly describes how to automate daily credit usage alerts using Snowflake tasks and notifications?

A 3,1,2,4

B 1,2,3,4

C 2,1,3,4

D 1,3,2,4

💡 Hint

Think about the logical order of creating queries, scheduling, storing, and notifying.

First create the query, then schedule it with a task, store results, and finally trigger notifications based on stored data.

✅ Best Practice

expert

Optimizing credit usage monitoring for cost control

Which approach best helps minimize credit usage while maintaining accurate monitoring of warehouse consumption?

A Schedule credit usage queries to run hourly and aggregate results daily to reduce query frequency

B Run credit usage queries continuously every minute for real-time accuracy

C Disable warehouse metering history to save storage costs

D Use manual ad-hoc queries only when billing issues arise

💡 Hint

Balance monitoring frequency with cost impact.

Running queries hourly and aggregating daily reduces compute cost while keeping monitoring timely enough for cost control.