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

Question

Options

• ARow access policies limit data visibility based on user privileges.
• BDynamic Data Masking doesn't influence dashboard creation.
• CThey offer unrestricted data visibility for all users.
• DBoth policies restrict data visibility for better security.

• A
  86% (19)
• B
  5% (1)
• C
  9% (2)

Explanation

Option A is correct because row access policies enforce role-based row filtering at the policy level, meaning users querying a report or dashboard only see the rows their privileges permit - the underlying query returns different result sets depending on who runs it, making this a foundational concern in report design and maintenance.

B is wrong because Dynamic Data Masking does influence dashboard output - it replaces sensitive column values (e.g., credit card numbers, SSNs) with masked placeholders for unauthorized users, so the same dashboard can display different data depending on the viewer's role.

C is wrong because it directly contradicts the purpose of both features; they exist precisely to restrict visibility, not grant it universally.

D is wrong because while both features do improve security, it conflates two distinct mechanisms - row access policies filter which rows are returned, while Dynamic Data Masking controls what values are shown within those rows. Treating them as identical oversimplifies their behavior and misses the nuance the exam is testing.

Memory tip: Think "rows vs. values" - Row Access Policies control row visibility (you see fewer rows), Dynamic Data Masking controls value visibility (you see masked values in the rows you can access). Option A is the only answer that accurately names one of these mechanisms.

No community discussion yet for this question.