Question 450
Consider this Snowflake situation: A dynamic table repeatedly misses its freshness objective after its source transformation became expensive. Which platform behavior BEST explains the appropriate solution?
Explanation
Correct Answer
The decisive Snowflake behavior is: A target-lag setting is an objective, not a guarantee independent of query and resource performance. It supports the response: Inspect dynamic table refresh history, upstream dependencies, and warehouse capacity before tuning target lag. Confirm it with this observable result: A controlled refresh meets the measured target after an evidence-based adjustment. Distinguish this mechanism from superficially related Snowflake features.
Incorrect Answers
The offered statement is true for this other mechanism: Snowpipe can process arriving staged files in serverless micro-batches based on configured notifications. It does not explain the facts described here, which follow from: A target-lag setting is an objective, not a guarantee independent of query and resource performance.
Driver compatibility and identity settings affect client connectivity independently of table permissions. That explanation applies to a different technical failure. Here the controlling principle is: A target-lag setting is an objective, not a guarantee independent of query and resource performance.
The offered statement is true for this other mechanism: COPY INTO loads compatible staged files into a table using a defined file format and appropriate privileges. It does not explain the facts described here, which follow from: A target-lag setting is an objective, not a guarantee independent of query and resource performance.