Which one of the following does not shows key similarities and differences between tables, regular views, cached query results, and materialized views while choosing any of them by David?

David, a Lead Data engineer with XYZ company looking out to improve query performance & other benefits while working with Tables, Regular Views, MVs and Cached Results.

Which one of the following does not shows key similarities and differences between tables, regular views, cached query results, and materialized views while choosing any of them by David?
A . Regular views do not cache data, and therefore cannot improve performance by caching.
B . As with non-materialized views, a materialized view automatically inherits the privileges of its base table.
C . Cached Query Results: Used only if data has not changed and if query only uses deterministic functions (e.g. not CURRENT_DATE).
D . Materialized views are faster than tables because of their “cache” (i.e. the query results for the
view); in addition, if data has changed, they can use their “cache” for data that hasn’t changed and use the base table for any data that has changed.
E . Both materialized views and regular views enhance data security by allowing data to be exposed or hidden at the row level or column level.

View Answer

Answer: B

Explanation:

Materialized Views, like other database objects (tables, views, UDFs, etc.), are owned by a role and have privileges that can be granted to other roles.

You can grant the following privileges on a materialized view:

SELECT

As with non-materialized views, a materialized view does not automatically inherit the privileges of its base table. You should explicitly grant privileges on the materialized view to the roles that should use that view.

As with non-materialized views, a user who wishes to access a materialized view needs privileges only on the view, not on the underlying object(s) that the view references. Rest is correct.