Question 20
For this Snowflake situation — A shared reporting warehouse is saturated by one batch workload and causes inconsistent response times for unrelated analysts. — the team adopts: Isolate the batch workload on its own warehouse instead of assuming every query must share one compute pool. Which ongoing practice BEST limits the same problem recurring?
Explanation
Correct Answer
The relevant ongoing safeguard is: Reassess workload isolation when new high-volume jobs are scheduled. It controls the recurring exposure associated with this mechanism: Independent Snowflake warehouses reduce compute contention for the same stored datasets. The original action, isolate the batch workload on its own warehouse instead of assuming every query must share one compute pool., still needs operational checks when the environment or workload changes.
Incorrect Answers
The suggested review tracks a different technical risk: Snowflake's shared data layer permits multiple compute clusters to access one logical dataset. Here the sustained control must address: Independent Snowflake warehouses reduce compute contention for the same stored datasets. Choose “Reassess workload isolation when new high-volume jobs are scheduled”.
That safeguard is relevant to: Sequences are database schema objects used to generate ordered numeric values, not warehouse resources. The current failure instead follows from: Independent Snowflake warehouses reduce compute contention for the same stored datasets. Its prevention measure is “Reassess workload isolation when new high-volume jobs are scheduled”.
This routine guards against another mechanism: Multi-cluster scaling policies trade responsiveness of adding clusters against compute spend. The recurring exposure in the current case is: Independent Snowflake warehouses reduce compute contention for the same stored datasets. The matching preventive check is “Reassess workload isolation when new high-volume jobs are scheduled”.