Home › Certifications › Snowflake SnowPro Core › Storage, Micro-partitions and Caching
24 multiple-choice questions and 17 flashcards on Storage, Micro-partitions and Caching, about 8% of the Snowflake SnowPro Core bank. Every one carries a written rationale.
Storage, Micro-partitions and Caching is one of 9 chapters in CoStudy's Snowflake SnowPro Core bank, and it holds 24 of the bank's 301 multiple-choice questions — roughly 8% of the total. That proportion is not arbitrary: chapters follow the certifying body's published exam outline, and the number of questions in each is set by that domain's published weight, so the share of your practice time this chapter takes matches the share of the real exam it accounts for.
Studying by chapter is worth doing once you have a diagnostic score. A single overall percentage tells you whether you are close; it does not tell you which domain is dragging. Working a weak chapter in isolation, and re-testing it in isolation, is the fastest way to move a score that has stalled — and it is why the mock exams in CoStudy report by domain rather than as one number.
3 questions drawn from this chapter, with the full rationale shown — the controlling principle behind the right answer, and why each wrong option tempts and fails.
Micro-partitions in Snowflake are:
Answer: B — Immutable compressed columnar files of ~50-500 MB each
B) Correct — Snowflake automatically creates immutable, columnar, compressed micro-partitions as data is loaded. A) Creation and sizing are automatic. C) They live in cloud object storage. D) Updates write new micro-partitions rather than editing existing ones.
Snowflake's Unistore initiative is built on which table type?
Answer: C — Hybrid tables combining row and column storage
C) Correct — Unistore is built on hybrid tables, which pair row-oriented storage for fast point operations with columnar storage for analytics. A) External tables are read-only. B) Iceberg is open-format integration. D) Temporary tables are just session-scoped.
What is the result of dividing a table-level Time Travel from 90 days to 0 days?
Answer: D — Versions outside the new window stop being available to queries
D) Correct — shortening retention means older versions fall outside the window and can no longer be reached by Time Travel queries. A) The framing overstates an immediate purge guarantee. B) Changing the parameter definitely changes behavior. C) Fail-safe depends on table type, not on this setting.
4 cards from the 17 in this chapter.
Compare permanent, transient and temporary tables with respect to Time Travel and Fail-safe, and state what zero-copy cloning does.
Permanent: up to 90 days Time Travel plus 7-day Fail-safe. Transient: 0-1 day Time Travel, no Fail-safe. Temporary: session-scoped, 0-1 day Time Travel, no Fail-safe. Zero-copy cloning creates a new object that references the same micro-partitions, so it consumes no extra storage until either copy is modified.
What are the Time Travel retention limits by edition, and what are the three SQL constructs used to query historical data?
Standard Edition allows 0 or 1 day; Enterprise and above allow 0 to 90 days for permanent objects. Historical data is queried with AT, BEFORE, and the UNDROP command restores dropped objects.
Name Snowflake's three caches, where each lives, and what each stores.
Metadata cache — in cloud services, holds object statistics so some queries resolve without compute. Result cache — in cloud services, holds full query results for 24 hours and is reusable across users and warehouses. Local disk (warehouse) cache — SSD on the warehouse nodes, holds micro-partition data and is lost when the warehouse suspends.
Result cache?
Stores recent query results for 24 hours. Identical query (same warehouse not required) returns cached result instantly.
These are a sample. The full Storage, Micro-partitions and Caching chapter runs 41 items with per-chapter progress tracking, on the web and in the iOS app.
Open Snowflake SnowPro Core in CoStudy →