Question 350
Consider this Snowflake situation: A scheduled reporting process burns credits because an orchestration tool repeatedly retries queries after success. Which platform behavior BEST explains the appropriate solution?
Explanation
Correct Answer
The decisive Snowflake behavior is: Repeated executions may consume additional warehouse compute independently of whether the result is identical. It supports the response: Inspect query history and orchestration logs for duplicate runs, then correct the retry behavior. Confirm it with this observable result: A controlled test issues the intended number of queries and the excessive retry volume disappears. Distinguish this mechanism from superficially related Snowflake features.
Incorrect Answers
The offered statement is true for this other mechanism: Compute scaling has cost-performance tradeoffs that cannot be inferred from a single duration metric. It does not explain the facts described here, which follow from: Repeated executions may consume additional warehouse compute independently of whether the result is identical.
This principle describes a separate cause: Snowflake role-based access control separates authentication from authorization on database objects. The reported condition is governed by: Repeated executions may consume additional warehouse compute independently of whether the result is identical. The two mechanisms should not be conflated.
Governance metadata can record relevant query access and object usage for investigation. That explanation applies to a different technical failure. Here the controlling principle is: Repeated executions may consume additional warehouse compute independently of whether the result is identical.