Question 690
After the approved change, engineers revisit: A team needs rapid load experimentation but permanently sets a high warehouse size after the one-time bulk import. Which result establishes the intended state?
Explanation
Correct Answer
The initial load meets timing while routine daily credits return to expected normal levels. This validates the relevant action: Temporarily size the warehouse for the bulk load and restore a measured right-sized baseline afterwards. The underlying Snowflake behavior is: Warehouse size can be adjusted without rebuilding stored data and need not remain oversized.
Incorrect Answers
Overnight cluster usage reduces while peak-time workloads still scale within limits. This evidence tests a DIFFERENT situation: A multi-cluster warehouse has a large fixed minimum cluster count during a quiet overnight period. The correction required in this case is: Temporarily size the warehouse for the bulk load and restore a measured right-sized baseline afterwards.
The test warehouse consumption appears under the intended monitor, without affecting unrelated workloads. This evidence tests a DIFFERENT situation: A service warehouse is accidentally configured with the wrong resource monitor and exhausts another team's credit allowance. The correction required in this case is: Temporarily size the warehouse for the bulk load and restore a measured right-sized baseline afterwards.
The clone is initially created quickly with shared underlying storage, while later mutations may increase billed storage. This evidence tests a DIFFERENT situation: A developer clones a large table for integration testing and budgets for an immediate full physical data copy. The correction required in this case is: Temporarily size the warehouse for the bulk load and restore a measured right-sized baseline afterwards.