DA0-002 Visualization and Reporting Practice Question
A data analyst is creating a self-service reporting environment. Which data governance practice ensures users see only data relevant to their department?
⚠ Common exam trap
Watch out — candidates often confuse data governance practices that manage metadata or consistency (like data lineage or single version of truth) with those that enforce access control (like row-level security). Candidates might pick 'data dictionary' thinking it restricts access, but it only documents data.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Row-level security
Row-level security (RLS) is a data governance practice that restricts data access at the row level based on user attributes such as department, role, or region. It ensures that users see only the data relevant to their department by dynamically filtering rows according to predefined policies. This is implemented in many BI and database platforms (e.g., Power BI, Tableau, Snowflake) and directly addresses the requirement of self-service reporting with department-specific data visibility.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Data lineage
Why it's wrong here
Data lineage traces the origin and transformation path of data; it records provenance rather than restricting which records a user can see. It tempts because lineage aids impact analysis and audit in self-service environments, but departmental visibility is enforced through permissions, not lineage documentation.
- ✓
Row-level security
Why this is correct
Row-level security filters individual rows by predicate, so each user's query returns only records matching their department. Unlike object-level permissions, which grant whole tables, RLS enforces the departmental constraint inside the query itself, satisfying the self-service requirement without duplicating datasets.
- ✗
Data dictionary
Why it's wrong here
A data dictionary documents field names, types and meanings; it describes metadata rather than enforcing who may query which records. It tempts because it supports self-service users in interpreting data correctly, but it cannot restrict a department's visibility, which requires access-control rules.
- ✗
Single version of truth
Why it's wrong here
A single version of truth standardises definitions and values across the organisation; it does not restrict which rows a department can view. It tempts because consistent shared metrics underpin trustworthy self-service reporting, but row-level or object-level access control is what limits visibility by department.
Go deeper
Related to this question
About these practice questions
One of 1,004 original DA0-002 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This DA0-002 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DA0-002 exam.