Question 670
For an e-commerce operations team, the original problem was: A query suddenly slows after a large table changed, yet the team looks only at warehouse size changes. What observation confirms success?
Explanation
Correct Answer
The investigation links performance change to a documented scan or join behavior difference. This validates the relevant action: Compare Query Profile, partition counts and data distribution before attributing regression to compute. The underlying Snowflake behavior is: Data growth, clustering drift or cardinality changes can alter query work with unchanged warehouse size.
Incorrect Answers
After an appropriate improvement, comparable queries scan fewer relevant partitions with correct row results. This evidence tests a DIFFERENT situation: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval. The correction required in this case is: Compare Query Profile, partition counts and data distribution before attributing regression to compute.
An optimized workload reduces avoidable compilation overhead without changing query results. This evidence tests a DIFFERENT situation: A performance report shows high compilation time but almost zero actual execution time for repeated short statements. The correction required in this case is: Compare Query Profile, partition counts and data distribution before attributing regression to compute.
A new event category follows the documented behavior rather than silently corrupting existing columns. This evidence tests a DIFFERENT situation: An analyst pivots event records to monthly metrics but assumes unexpected new event categories appear automatically in a fixed static pivot. The correction required in this case is: Compare Query Profile, partition counts and data distribution before attributing regression to compute.