Question 640
For this Snowflake situation — A team dropped a production table recently and wants to restore it without rebuilding the data from exported files. — the team adopts: Use UNDROP TABLE when the object is still eligible under Time Travel retention. Which ongoing practice BEST limits the same problem recurring?
Explanation
Correct Answer
The relevant ongoing safeguard is: Check retention eligibility before executing destructive DDL changes. It controls the recurring exposure associated with this mechanism: Snowflake supports restoring eligible dropped objects during their configured Time Travel period. The original action, use UNDROP TABLE when the object is still eligible under Time Travel retention., still needs operational checks when the environment or workload changes.
Incorrect Answers
This routine guards against another mechanism: Time Travel permits user-accessible historical queries while the relevant table version remains within retention. The recurring exposure in the current case is: Snowflake supports restoring eligible dropped objects during their configured Time Travel period. The matching preventive check is “Check retention eligibility before executing destructive DDL changes”.
The suggested review tracks a different technical risk: Reader accounts enable supported share consumption for organizations that do not operate their own Snowflake accounts. Here the sustained control must address: Snowflake supports restoring eligible dropped objects during their configured Time Travel period. Choose “Check retention eligibility before executing destructive DDL changes”.
This routine guards against another mechanism: Discovery through a listing does not eliminate provider object authorization and product access controls. The recurring exposure in the current case is: Snowflake supports restoring eligible dropped objects during their configured Time Travel period. The matching preventive check is “Check retention eligibility before executing destructive DDL changes”.