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

Question

Options

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

• B
  4% (1)
• C
  92% (24)
• D
  4% (1)

Explanation

Row access policies control which rows a user can see based on their privileges, meaning two users running the same report or dashboard query against the same table will see different subsets of data - making C the precise, accurate answer. Dynamic Data Masking (DDM), by contrast, operates at the column level, obscuring specific field values (e.g., showing **** instead of a SSN) rather than filtering entire rows, so it absolutely does impact dashboards - eliminating A. Option B is wrong because both mechanisms exist specifically to restrict visibility, not enhance it freely. Option D is too broad: while both are security tools, they work differently - DDM masks column values while row access policies filter rows - and the question asks specifically about what affects report/dashboard creation, which DDM does affect but not in the same way as row policies.

Memory tip: Think "Row = Restricts Rows" - row access policies are about who sees which records, like a bouncer checking IDs at the door. DDM is more like a redaction pen that blacks out sensitive words on a page everyone can already read. The exam question targets the row-level distinction, so lock in: row policy = row visibility = user privilege-based filtering.

No community discussion yet for this question.