Which of the following are benefits of micro-partitioning? (Select TWO)

Question

Options

• AMicro-partitions cannot overlap in their range of values
• BMicro-partitions are immutable objects that support the use of Time Travel.
• CMicro-partitions can reduce the amount of I/O from object storage to virtual warehouses
• DRows are automatically stored in sorted order within micro-partitions
• EMicro-partitions can be defined on a schema-by-schema basis

• A
  5% (2)
• B
  86% (38)
• D
  7% (3)
• E
  2% (1)

Explanation

B is correct: Micro-partitions are immutable. When data is modified, Snowflake creates new micro-partitions rather than overwriting old ones. The original partitions are retained, which is what enables Time Travel and Fail-safe. C is correct: Because each micro-partition stores metadata (min/max values per column), Snowflake can prune irrelevant partitions at query time - skipping them entirely rather than loading them from object storage, reducing I/O. The distractors are wrong: micro-partitions CAN overlap in value ranges (unlike traditional range partitioning, which is a deliberate design difference). Rows are stored in insertion order, not sorted. And micro-partitioning is automatic and table-wide, not configurable per schema.

No community discussion yet for this question.