How do row access policies and Dynamic Data Masking affect the creation and maintenance of reports and dashboards?

Question

Options

• ABoth policies restrict data visibility for better security.
• BDynamic Data Masking doesn't impact dashboard creation or maintenance.
• CRow access policies limit data visibility based on user privileges.
• DThey enhance data visibility without any restrictions.

• C
  93% (14)
• D
  7% (1)

Explanation

Option C is correct because row access policies function as dynamic filters that restrict which rows appear in query results based on the querying user's role or privileges - meaning two users running the same report or dashboard query can see entirely different subsets of data, directly impacting what gets surfaced in BI tools.

Why the distractors fail:

• A is misleading by grouping both features together as equivalent. While both involve data governance, Dynamic Data Masking operates at the column level (obfuscating values like showing **** instead of a SSN), whereas row access policies operate at the row level - they are distinct mechanisms with different scopes.
• B is incorrect because DDM absolutely affects dashboards - when column values are masked, aggregations, filters, and visualizations built on those columns behave differently for different users, creating maintenance complexity.
• D is the opposite of reality; both features are specifically designed to restrict what data is exposed, not broaden it.

Memory tip: Use the acronym R-C: Row access policies control Rows (who sees which records), while Dynamic Data Masking controls Masked columns (how values appear). Reports are affected because what you see depends on your privilege level - row policies filter entire records, making them invisible to unauthorized users in any report or dashboard.

No community discussion yet for this question.