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.
Answer: D
Explanation:
Among the options provided, the incorrect statement (and thus not a limitation) is:
D. A materialized view can query only a single table & Joins, including self-joins, are not supported.
Materialized views in Snowflake can indeed be based on the result of a query that includes JOIN operations on one or more tables.
Latest DEA-C01 Dumps Valid Version with 100 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund