Which one is not the limitation he must be aware of before using MVs in their use case?

Data Engineer identified use case where he decided to use materialized view for query performance.

Which one is not the limitation he must be aware of before using MVs in their use case?
A . Truncating a materialized view is not supported.
B . Time Travel is not currently supported on materialized views.
C . You cannot directly clone a materialized view by using the CREATE MATERIAL-IZED VIEW … CLONE… command.
D . A materialized view can query only a single table & Joins, including self-joins, are not supported.
E . A materialized views does not support clustering.
F . A materialized views cannot be created on Shared Data.
G . A materialized view cannot include HAVING clauses OR ORDER BY clause.
H . Context Functions like CURRENT_TIME or CURRENT_TIMESTAMP is not per-mitted.

View Answer

Answer: E, G

Explanation:

Defining a clustering key on a materialized view is supported and can increase performance in many situations. However, it also adds costs.

If you cluster both the materialized view(s) and the base table on which the materialized view(s) are defined, you can cluster the materialized view(s) on different columns from the columns used to cluster the base table.

You can create a materialized view on shared data.

Also You can use Snowflake’s data sharing feature to share a materialized view.

Rest all are correct.