Question 340
For this Snowflake situation — A finance team is surprised by an increase in storage costs after many tables were cloned and frequently updated. — the team adopts: Analyze retained storage from table history and diverged micro-partitions rather than assuming every clone copies full data instantly. Which ongoing practice BEST limits the same problem recurring?
Explanation
Correct Answer
The relevant ongoing safeguard is: Review clone cleanup and data retention after test-environment refreshes. It controls the recurring exposure associated with this mechanism: Zero-copy clones initially share storage but later writes and retention can increase billed storage. The original action, analyze retained storage from table history and diverged micro-partitions rather than assuming every clone copies full data instantly., still needs operational checks when the environment or workload changes.
Incorrect Answers
This routine guards against another mechanism: Warehouse-level credit records make usage-based chargeback possible when ownership is governed. The recurring exposure in the current case is: Zero-copy clones initially share storage but later writes and retention can increase billed storage. The matching preventive check is “Review clone cleanup and data retention after test-environment refreshes”.
The suggested review tracks a different technical risk: Snowflake's system-defined administrative roles divide identity and grant management from ordinary object creation. Here the sustained control must address: Zero-copy clones initially share storage but later writes and retention can increase billed storage. Choose “Review clone cleanup and data retention after test-environment refreshes”.
That safeguard is relevant to: Privacy-preserving collaboration can expose approved aggregate outcomes while constraining raw data visibility. The current failure instead follows from: Zero-copy clones initially share storage but later writes and retention can increase billed storage. Its prevention measure is “Review clone cleanup and data retention after test-environment refreshes”.