Question 430
A table-scan query runs faster a second time on the same still-running warehouse even though results differ. After implementing the approach, which observation best demonstrates the required outcome?
Explanation
Correct Answer
Subsequent scans benefit from data already in the warehouse's cache. This demonstrates the outcome for the stated requirement rather than just a saved configuration.
Incorrect Answers
Queries read the expected nested values without string-splitting the original document. That measures a different outcome: a staging table stores raw JSON text but downstream queries require typed access to nested attributes. In this case, verify that subsequent scans benefit from data already in the warehouse's cache.
The pipeline generates the correct joined result while avoiding a complete local materialization. That measures a different outcome: a Python developer wants to filter and join large Snowflake DataFrames without pulling all rows into pandas. In this case, verify that subsequent scans benefit from data already in the warehouse's cache.
The relevant dashboard query reuses the maintained result with lower total runtime. That measures a different outcome: an aggregate dashboard repeatedly runs an expensive compatible query over slowly changing source data. In this case, verify that subsequent scans benefit from data already in the warehouse's cache.





SnowPro Core COF-C03 Practice Tests