How do row access policies and Dynamic Data Masking impact the creation of dashboards in terms of data visibility and security?

Question

Options

• ADynamic Data Masking doesn't affect data visibility in dashboards.
• BBoth policies restrict data visibility for better security.
• CThey improve data visibility for all users without restrictions.
• DRow access policies limit data visibility based on user privileges.

• A
  4% (2)
• C
  2% (1)
• D
  94% (47)

Explanation

D is correct because row access policies filter which rows a user can see based on their privileges - when a dashboard queries data, those filters apply automatically, so different users see different subsets of the data depending on their role or attributes.

Why the distractors fail:

• A is wrong because Dynamic Data Masking does affect data visibility - it obscures or replaces sensitive column values (e.g., showing XXX-XX-1234 instead of a full SSN) for users without the appropriate privileges.
• B is partially misleading - both policies do restrict visibility, but they work differently: row policies filter rows, masking policies filter column values. The question asks specifically about dashboards, and the key mechanism is row-level restriction tied to user privileges, making D more precise.
• C is the opposite of reality - neither policy improves visibility for all users; both are security controls that limit what users can see.

Memory tip: Think "Row = Rows you're allowed to read, Masking = Masked column values" - both restrict, but row access policies are the ones that directly limit how many records appear in a dashboard based on who's logged in.

No community discussion yet for this question.