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

Question

Options

• ADynamic Data Masking doesn't influence dashboard creation.
• BThey enhance data visibility for all users without limitations.
• CRow access policies limit data visibility based on user privileges.
• DBoth policies restrict data visibility for better security.

• B
  3% (1)
• C
  94% (32)
• D
  3% (1)

Explanation

Row access policies control which rows a user can see based on their privileges or role, meaning two users viewing the same dashboard will see different subsets of data - making C the precise, correct answer.

Why the distractors fail:

• A is wrong because Dynamic Data Masking (DDM) does affect dashboards - it masks column values (e.g., showing XXX-XX-1234 instead of a full SSN) based on user role, directly shaping what dashboard viewers see.
• B is the opposite of reality; both mechanisms restrict visibility rather than granting universal access.
• D is a tempting trap - both policies do improve security, but DDM works at the column level (masking values), not row-level restriction, so saying both "restrict data visibility" conflates two distinct mechanisms and overstates DDM's role.

Memory tip: Think of it as a table: Row access policy = controls rows (who sees which records); DDM = controls columns (who sees the real values). Only row access policies restrict which data exists in a dashboard view - DDM just obscures the display of values that are already visible.

No community discussion yet for this question.