Question 250
A test plan evaluates: An analyst expects to run SELECT AT a historical timestamp after Time Travel retention has expired into Fail-safe. Which evidence should be required before release?
Explanation
Correct Answer
A test within the allowed retention works, while a query beyond retention is not promised. This validates the relevant action: Explain that historical SQL query access ends with Time Travel and use the proper support escalation only if Fail-safe applies. The underlying Snowflake behavior is: Fail-safe is not user-accessible historical querying; it is a Snowflake-managed recovery period.
Incorrect Answers
The selected retention setting is accepted without unsupported edition assumptions. This evidence tests a DIFFERENT situation: A team increases Time Travel retention to 90 days on a Standard Edition account without checking edition limits. The correction required in this case is: Explain that historical SQL query access ends with Time Travel and use the proper support escalation only if Fail-safe applies.
Recovered table data matches the point within its permitted Time Travel retention window. This evidence tests a DIFFERENT situation: A developer asks to recover a table dropped yesterday within its configured retention window. The correction required in this case is: Explain that historical SQL query access ends with Time Travel and use the proper support escalation only if Fail-safe applies.
A controlled nearest-neighbor example orders relevant embedding vectors by the intended similarity measure. This evidence tests a DIFFERENT situation: An application stores vector embeddings but a developer expects standard string comparison to rank semantic similarity automatically. The correction required in this case is: Explain that historical SQL query access ends with Time Travel and use the proper support escalation only if Fail-safe applies.