Question 500
For this Snowflake situation — A dashboard repeatedly computes the same aggregate over a large base table and needs predictable refresh-aware response times. — the team adopts: Evaluate an eligible materialized view that maintains the required aggregate and measure maintenance overhead. Which ongoing practice BEST limits the same problem recurring?
Explanation
Correct Answer
The relevant ongoing safeguard is: Monitor view refresh cost and query plans when source tables evolve. It controls the recurring exposure associated with this mechanism: Materialized views can persist precomputed results for qualifying workloads rather than recalculating every aggregate. The original action, evaluate an eligible materialized view that maintains the required aggregate and measure maintenance overhead., still needs operational checks when the environment or workload changes.
Incorrect Answers
The suggested review tracks a different technical risk: The persisted query result cache may satisfy eligible repeat executions without rerunning warehouse computation. Here the sustained control must address: Materialized views can persist precomputed results for qualifying workloads rather than recalculating every aggregate. Choose “Monitor view refresh cost and query plans when source tables evolve”.
That safeguard is relevant to: CTEs organize query logic but do not themselves guarantee materialization or faster execution. The current failure instead follows from: Materialized views can persist precomputed results for qualifying workloads rather than recalculating every aggregate. Its prevention measure is “Monitor view refresh cost and query plans when source tables evolve”.
This routine guards against another mechanism: QUALIFY filters rows based on window-function results after analytic evaluation. The recurring exposure in the current case is: Materialized views can persist precomputed results for qualifying workloads rather than recalculating every aggregate. The matching preventive check is “Monitor view refresh cost and query plans when source tables evolve”.