How do materialized views differ from secure views in data analysis?

Question

Options

• ASecure views provide precomputed snapshots, unlike materialized views.
• BMaterialized views offer enhanced data security while allowing selective data access.
• CSecure views precompute data, unlike materialized views.
• DMaterialized views restrict data access for improved security.

• B
  2% (1)
• C
  93% (42)
• D
  4% (2)

Explanation

Option C is correct because secure views are defined with a SECURE keyword to hide the underlying SQL logic from users, but they still execute queries at runtime - they do not precompute or store data. Materialized views, by contrast, physically store the query results and must be refreshed to reflect new data, making them a precomputed snapshot rather than a live query.

Why the distractors are wrong:

• A reverses the roles - materialized views provide precomputed snapshots, not secure views.
• B conflates both concepts; materialized views are about performance (precomputed storage), not security.
• D describes what secure views do (restrict/hide data), not materialized views.

Memory tip: Think Materialized = Memorized (the data is stored/cached), and Secure = Shielded (the logic is hidden, but nothing is precomputed). "Materialized" literally means "made physical" - the result set exists as a real stored object.

No community discussion yet for this question.