Snowflake's query optimizer can automatically rewrite eligible queries to access materialized views instead of scanning their underlying base tables. However, the existence of a matching materialized view does not guarantee that it will be selected.
Option B correctly identifies the optimizer's cost-based decision process.
Snowflake evaluates available execution strategies and may choose to scan the base table when doing so is expected to provide equivalent or better performance. For example, effective micro-partition pruning on a well-clustered base table can make direct access more efficient than using a materialized view.
Option A is incorrect as an explanation of this behavior. Although Snowflake imposes restrictions on materialized-view definitions, including joins, the optimizer can still use materialized views when optimizing eligible queries involving other tables.
Option C is incorrect because materialized-view maintenance does not require queries to return stale data. Snowflake can reconcile changes from the base table to provide current results.
Option D incorrectly assumes that materialized views always outperform base-table access.
Administrators should inspect EXPLAIN output and Query Profile to determine whether the optimizer selects a materialized view. They should also account for automatic materialized-view maintenance costs when evaluating overall performance and credit efficiency.
Official Snowflake references: Working with Materialized Views: How the Query Optimizer Uses Materialized Views.
Submit