Exam SnowPro Core topic 1 question 294 discussion

Answer -- BC

As wrote here: https://docs.snowflake.com/en/user-guide/tables-clustering-micropartitions.html#benefits-of-micro-partitioning - In contrast to traditional static partitioning, Snowflake micro-partitions are derived automatically; they don’t need to be explicitly defined up-front or maintained by users. - As the name suggests, micro-partitions are small in size (50 to 500 MB, before compression), which enables extremely efficient DML and fine-grained pruning for faster queries. - Micro-partitions can overlap in their range of values, which, combined with their uniformly small size, helps prevent skew. - Columns are stored independently within micro-partitions, often referred to as columnar storage. This enables efficient scanning of individual columns; only the columns referenced by a query are scanned. So - A is False (3rd point) - D is False because the sort is decided from "how the data is inserted" - E is False (1st point)

BC are correct

correct

Correct

Micro-partitions can overlap. No relationship to Time Travel. Sort is based on Data Ans = C D (Though rows are mapped not not sorted)

B & C A.CAN OVERLAP D.micropartitions are created based on the order of the data loaded/inserted. Data are not sorted within micropart. E.are automatically derived based on the data, no schemas

Answer is A & B https://docs.snowflake.com/en/user-guide/tables-clustering-micropartitions.html

C&D I think