Answer-first summary for fast verification
Answer: Make the dimension tables transient with a retention period of 0 days, and backup the table daily to a permanent table. Delete all but the latest backup.
The question asks for the recommended approach to manage costs for frequently changing dimension tables. Option B is optimal because it addresses the core issue: high-churn dimension tables can incur excessive Continuous Data Protection (CDP) costs through Time Travel and Fail-safe. Making tables transient with 0-day retention eliminates these costs, while daily backups to a permanent table ensure data protection. This aligns with Snowflake's documentation on managing costs for large, high-churn tables. Option A is less suitable as it retains Time Travel (up to 7 days), which still incurs CDP costs. Option C is incorrect because transient tables cannot be cloned into permanent tables. Option D is inefficient due to weekly replication and permanent storage with Time Travel, which doesn't minimize costs effectively. The community discussion supports B, with the highest upvoted comment citing Snowflake's best practices.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
When working with dimension tables that change frequently, what is the recommended approach for managing costs?
A
Keep the Time Travel retention period for the dimension tables to 7 days or less.
B
Make the dimension tables transient with a retention period of 0 days, and backup the table daily to a permanent table. Delete all but the latest backup.
C
Make the dimension tables transient and back-up the data daily into a permanent table using cloning.
D
Make the dimension tables permanent with a retention period of 7 days. Replicate the database to a secondary database once a week.
No comments yet.