Question

A data engineer creates a materialized view on a very large fact table to speed up a frequently run dashboard aggregation. After deployment, the base table receives heavy, continuous DML (thousands of inserts and updates per hour). The team notices unexpected serverless credit consumption even during periods when no one is querying the dashboard. What is the MOST likely cause of this credit consumption?

Accepted Answer

The materialized view is being automatically maintained by a Snowflake-managed background service that consumes serverless credits as the base table changes.

Answer

The materialized view keeps the querying virtual warehouse running continuously to serve results from cache.

Answer

Each dashboard query against the materialized view triggers a full re-scan of the base table, consuming warehouse credits.

Answer

The result cache backing the materialized view is being refreshed every 24 hours, incurring recurring compute charges.