I agree with C & D.
https://docs.snowflake.com/en/user-guide/views-materialized.html#effects-of-changes-to-base-tables-on-materialized-views
Answer-c --> When a base table changes, all materialized views defined on the table are updated by a background service that uses compute resources provided by Snowflake.
https://docs.snowflake.com/en/user-guide/views-materialized#label-materialized-views-maintenance-billing
Answer CD as per the evidence in the link, user queries does not come under maintenance
C and E
Materialized views impact your costs for both storage and compute resources:
Storage: Each materialized view stores query results, which adds to the monthly storage usage for your account.
Compute resources: In order to prevent materialized views from becoming out-of-date, Snowflake performs automatic background maintenance of materialized views. When a base table changes, all materialized views defined on the table are updated by a background service that uses compute resources provided by Snowflake.
This one make more sense
I found this in Snowflake Doc :
Materialized Views and Clustering
Defining a clustering key on a materialized view is supported and can increase performance in many situations. However, it also adds costs.
https://docs.snowflake.com/en/user-guide/views-materialized#label-materialized-views-maintenance-billing
C and E
Materialized views impact your costs for both storage and compute resources:
Storage: Each materialized view stores query results, which adds to the monthly storage usage for your account.
Compute resources: In order to prevent materialized views from becoming out-of-date, Snowflake performs automatic background maintenance of materialized views. When a base table changes, all materialized views defined on the table are updated by a background service that uses compute resources provided by Snowflake.
I would rather go with the highly voted answers (C&D) and not the key provided (D&E) based on the Snowflake Guide: https://docs.snowflake.com/en/user-guide/views-materialized.html#effects-of-changes-to-base-tables-on-materialized-views
In general, the costs are proportional to:
The number of materialized views created on each base table, and the amount of data that changes in each of those materialized views when the base table changes. Any changes to micro-partitions in the base table require eventual materialized view maintenance, whether those changes are due to reclustering or DML statements run on the base table.
The number of those materialized views that are clustered. Maintaining clustering (of either a table or a materialized view) adds costs.
https://docs.snowflake.com/en/user-guide/views-materialized.html#effects-of-changes-to-base-tables-on-materialized-views
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
tejarun
Highly Voted 2 years, 5 months agoJRayan
2 years, 3 months agoLavpak
2 years, 5 months agodamaldon
Most Recent 9 months ago_yyukta
1 year, 2 months ago[Removed]
1 year, 6 months agoSk_3
1 year, 7 months agoSk_3
1 year, 7 months agotitihab
1 year, 6 months agoMarge23
1 year, 7 months agosinghks
1 year, 8 months agootsumy
1 year, 9 months agostornati
1 year, 8 months agovrfidman
1 year, 7 months agoMultiCloudIronMan
1 year, 9 months agodmitriypo
2 years agoisolated_sniper
2 years agorneti
2 years, 1 month agopsilvabr
2 years, 2 months agoKarBiswa
2 years, 3 months agomlaus
2 years, 3 months agoSV1122
2 years, 4 months ago