What distinguishes Materialized views from Secure views in the context of data analysis?

Question

Options

• ASecure views provide a precomputed snapshot of data, unlike Materialized views.
• BMaterialized views restrict data access for security purposes, unlike Secure views.
• CMaterialized views enhance data security, while Secure views offer improved query performance.
• DSecure views provide enhanced data security without precomputing data.

• B
  3% (1)
• C
  6% (2)
• D
  90% (28)

Explanation

Option D is correct because Secure views are designed purely for access control - they hide sensitive columns or rows from certain users without storing any precomputed data, whereas Materialized views physically store the results of a query to speed up future reads.

• A is wrong because it reverses the definitions: it's Materialized views (not Secure) that store precomputed snapshots of data.
• B is wrong because Materialized views have nothing to do with restricting access; that's the role of Secure views.
• C is wrong because it swaps the purposes entirely - Materialized views are about performance, and Secure views are about security, not the other way around.

Memory tip: Think Materialized = Memory (it stores/caches data for speed), and Secure = Shield (it shields sensitive data from unauthorized eyes, no caching involved).

No community discussion yet for this question.