Browse Certification Practice Tests by Exam Family

CompTIA Data+ DA0-002: Data Governance

Try 10 focused CompTIA Data+ DA0-002 questions on Data Governance, with explanations, then continue with IT Mastery.

Open the matching IT Mastery practice page for timed mocks, topic drills, progress tracking, explanations, and full practice.

Try CompTIA Data+ DA0-002 on Web View full CompTIA Data+ DA0-002 practice page

Topic snapshot

FieldDetail
Exam routeCompTIA Data+ DA0-002
Topic areaData Governance
Blueprint weight14%
Page purposeFocused sample questions before returning to mixed practice

How to use this topic drill

Use this page to isolate Data Governance for CompTIA Data+ DA0-002. Work through the 10 questions first, then review the explanations and return to mixed practice in IT Mastery.

PassWhat to doWhat to record
First attemptAnswer without checking the explanation first.The fact, rule, calculation, or judgment point that controlled your answer.
ReviewRead the explanation even when you were correct.Why the best answer is stronger than the closest distractor.
RepairRepeat only missed or uncertain items after a short break.The pattern behind misses, not the answer letter.
TransferReturn to mixed practice once the topic feels stable.Whether the same skill holds up when the topic is no longer obvious.

Blueprint context: 14% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.

Sample questions

These original IT Mastery practice questions are aligned to this topic area. Use them for self-assessment, scope review, and deciding what to drill next.

Question 1

Topic: Data Governance

A data analyst is reviewing documentation for a monthly retention dashboard. Based on the data flow diagram excerpt, which interpretation is best supported?

Exhibit: Data flow diagram excerpt

CRM database ─┐
Billing CSV ──┼─> ETL: standardize customer_id, join accounts ─> Curated customer table ─> Retention dashboard
Support API ─┘
Survey tool ─> ETL: aggregate NPS by month ─> NPS summary table ────────────────┘
Retention dashboard ─> PDF export ─> Executive email

Options:

  • A. Billing data bypasses ETL and loads directly into the dashboard.

  • B. Customer, billing, and support data are joined before reaching the dashboard.

  • C. Survey responses are joined at the customer level in the curated table.

  • D. The executive email is an upstream source for the dashboard.

Best answer: B

Explanation: A data flow diagram shows direction of movement from sources, through processing steps, to outputs. In this exhibit, CRM, Billing CSV, and Support API all feed one ETL process that standardizes customer_id and joins accounts. That output becomes the curated customer table, which then feeds the retention dashboard. The survey tool follows a separate path: it is aggregated into an NPS summary table before also feeding the dashboard. The PDF export and executive email are downstream outputs from the dashboard, not upstream sources.

  • Upstream vs. downstream fails because the executive email appears after the dashboard as an output path.
  • Bypassing ETL fails because Billing CSV is shown entering the ETL step before any dashboard output.
  • Customer-level survey join fails because the survey path is aggregated by month into an NPS summary table, not joined into the curated customer table.

Question 2

Topic: Data Governance

A data team is preparing to release a daily sales dashboard to 2,000 regional managers. Functional testing passed with a small sample, but the dashboard must remain usable during the morning login surge.

Exhibit: Pre-release validation note

FindingDetail
Sample test5 users, 10,000 rows, passed
Expected peak800 concurrent users at 8:00 a.m.
Dataset size45 million rows after launch
Risk notedSlow refresh or timeout under peak use

Which quality assurance test should the team perform next?

Options:

  • A. Stress testing

  • B. Source control review

  • C. User acceptance testing

  • D. Unit testing

Best answer: A

Explanation: Stress testing is used when a data process, report, or system must be evaluated under heavy volume or load. The exhibit shows that basic functionality passed, but the unresolved risk is performance with 800 concurrent users and 45 million rows. That makes load behavior, refresh time, and timeout risk the deciding concern rather than calculation correctness or user sign-off.

The key takeaway is to match the QA method to the risk being tested: heavy usage and volume call for stress testing.

  • Unit testing checks individual calculations or components, but the exhibit’s concern is peak dashboard load.
  • User acceptance testing confirms business usability, but it does not specifically measure performance under heavy concurrency.
  • Source control review helps verify version history and change management, not runtime behavior at launch volume.

Question 3

Topic: Data Governance

A data team publishes a monthly sales performance report. Finance requires the team to reproduce any prior month’s report exactly as it was delivered and identify which dataset or calculation changes were made after delivery. Which approach best meets this requirement?

Options:

  • A. Create a data dictionary for all fields

  • B. Use versioned datasets and reports with change history

  • C. Restrict report access by department

  • D. Increase the report refresh frequency

Best answer: B

Explanation: Data versioning is a governance control used to track how datasets, reports, or analytical outputs change over time. In this scenario, Finance needs reproducibility and change traceability, so prior delivered reports should not be overwritten without a record. Versioned datasets, report files, calculations, or snapshots allow analysts to compare versions, identify when changes occurred, and reproduce the exact output used for a business decision. A data dictionary and access controls may support governance, but they do not preserve historical report states.

  • Refresh frequency affects how often data updates, but it does not preserve previous report versions.
  • Data dictionary documents field meaning, but it does not track report or dataset changes over time.
  • Access restriction protects who can view reports, but it does not provide reproducibility or change history.

Question 4

Topic: Data Governance

A data analyst supports an automated compliance report that flags customer accounts for manual review. The compliance team needs a nontechnical artifact showing which source fields are used, how risk-score transformations are applied, and why each rule can trigger a flag. The artifact must support audit review without documenting database administration details. Which documentation artifact is the best choice?

Options:

  • A. Entity-relationship diagram

  • B. Database backup schedule

  • C. Data explainability report

  • D. Refresh interval calendar

Best answer: C

Explanation: A data explainability report is the best fit when stakeholders need to understand how an automated decision or report output was produced. It can document the source fields, transformation logic, rule thresholds, and business rationale behind each flag in language suitable for compliance and nontechnical reviewers. This makes the automated process auditable and explainable without shifting into database operations or physical system design. A data dictionary or ERD may help define fields or relationships, but it does not fully explain why a rule-based output was generated. The key is choosing an artifact that connects data inputs and logic to the resulting decision.

  • Backup schedule focuses on recovery timing and retention, not report logic or automated decision rationale.
  • Entity relationships show table structure and relationships, but not why a compliance flag was triggered.
  • Refresh timing documents when data updates occur, not how transformations and rules create report outputs.

Question 5

Topic: Data Governance

A data analyst is investigating why two approved monthly sales reports show different totals for the same period. The analyst finds this validation note:

Exhibit: Report validation finding

ItemFinding
ReportMonthly Sales KPI
Same filterMarch 2026, all regions
Output saved April 2Total sales: $4,820,000
Output saved April 9Total sales: $4,910,000
Metadata presentOwner, refresh date
Missing controlDataset snapshot ID and report version

Which next action best addresses the governance issue shown in the exhibit?

Options:

  • A. Remove the refresh date from metadata

  • B. Convert the report to a static PDF

  • C. Mask the sales totals in the report

  • D. Implement dataset and report versioning

Best answer: D

Explanation: Data versioning is a governance control for tracking changes to datasets, reports, and analytical outputs over time. In this case, two reports use the same filter but show different totals, and the exhibit shows that the missing control is a dataset snapshot ID and report version. Adding versioning would let analysts identify whether the change came from updated source data, a revised calculation, or a modified report definition. Metadata such as owner and refresh date is useful, but it does not fully prove which exact dataset and report logic produced each approved output.

The key takeaway is that versioning supports traceability when numbers change across reporting cycles.

  • Removing metadata makes traceability worse because the refresh date is still useful governance information.
  • Static PDF delivery preserves one output but does not track dataset or report changes across versions.
  • Masking totals is a privacy control, not a control for explaining changed KPI values.

Question 6

Topic: Data Governance

A retail analytics team is creating a governed data mart for online transaction analysis. The dataset includes customer names, transaction amounts, full primary account numbers (PANs), expiration dates, and authorization results. Which compliance approach best maps to the protection obligation for this dataset?

Options:

  • A. Apply SOX controls for financial statements

  • B. Apply PCI DSS controls for cardholder data

  • C. Apply general data retention rules only

  • D. Apply HIPAA safeguards for patient records

Best answer: B

Explanation: PCI DSS applies when an organization stores, processes, or transmits payment card data. In this scenario, the presence of full PANs and expiration dates creates cardholder-data protection obligations, so governance planning should include PCI DSS-aligned controls such as limiting access, protecting stored cardholder data, and documenting handling requirements. Other frameworks may also matter in some environments, but the payment-card fields are the deciding fact here. A general retention policy is not enough because the dataset contains regulated cardholder data, not just ordinary transaction history.

  • HIPAA mismatch fails because the stem contains payment card data, not patient health information.
  • SOX mismatch fails because financial reporting controls do not specifically govern cardholder data protection.
  • Retention only fails because storage duration does not address the compliance and protection requirements for PANs.

Question 7

Topic: Data Governance

A data analyst is responding to an audit request for a sales dashboard. The auditor needs documentation that shows how the dashboard metric is produced and where it is used.

Exhibit: Audit request excerpt

Metric: Net Revenue
Sources: CRM opportunities + billing invoices
Need to show: source fields, joins, filters, calculated transformations,
and final dashboard/report locations
Purpose: trace the metric from origin to report output

Which documentation artifact best satisfies the request?

Options:

  • A. Data lineage documentation

  • B. Data classification matrix

  • C. Dashboard style guide

  • D. Data dictionary

Best answer: A

Explanation: Data lineage documentation is the best fit when the requirement is to trace a metric from its origin through integration, joins, filters, calculations, and final report usage. In this scenario, the auditor is not just asking what Net Revenue means; the request includes source systems, transformation logic, and downstream dashboard locations. That combination points to lineage because it documents the end-to-end path and supports auditability. A data dictionary can help define fields, but it does not normally show the workflow that moves and transforms data across systems into reports.

  • Field definitions only are useful for understanding names, data types, and meanings, but they do not trace transformations across the workflow.
  • Classification focus helps identify sensitivity or handling rules, not how a metric is integrated and calculated.
  • Presentation standards guide dashboard appearance and consistency, but they do not document source-to-report traceability.

Question 8

Topic: Data Governance

A data analyst rebuilds a monthly revenue report for audit requests. The operational sales database is the source of truth, but it is updated daily and can receive backdated corrections. Auditors must be able to reproduce the exact numbers that appeared in each published report without preventing normal source-system updates. Which control is the BEST professional decision?

Options:

  • A. Create a read-only monthly snapshot with extract metadata

  • B. Re-run the report against the live source database

  • C. Save only the final report PDF for each month

  • D. Ask the sales team to stop backdated corrections

Best answer: A

Explanation: Repeatability for reports rebuilt from changing data is improved by preserving the exact input version used for the published output. A read-only snapshot or versioned extract, paired with metadata such as source table, extract time, filters, and transformation version, lets analysts rebuild or validate the same report later. This supports auditability without freezing the operational system or replacing the source of truth. The live database remains the authoritative current source, while the snapshot documents the historical reporting state.

  • Live re-run fails because daily updates and backdated corrections can change the results.
  • PDF only preserves the output but not the data and logic needed to rebuild it.
  • Stopping corrections disrupts normal operations and does not provide a practical governance control.

Question 9

Topic: Data Governance

A data analyst is reviewing access activity for a shared analytics workspace. The workspace contains monthly customer extracts used for internal churn reporting.

Exhibit: Access log and classification note

Dataset: customer_churn_extract.csv
Classification: Confidential - contains customer email and phone
Storage location: Shared workspace / Public links enabled
Event 1: Link created by analyst account at 09:12
Event 2: Download from external IP at 09:27
Event 3: Security alert: Unapproved external access

What should the analyst do first?

Options:

  • A. Email affected customers with the log details

  • B. Report the event through the incident response process

  • C. Reclassify the dataset as public for future sharing

  • D. Delete the file and disable the public link

Best answer: B

Explanation: A suspected breach or security event involving confidential data should be reported immediately through the organization’s incident response process. The analyst has enough evidence to treat this as reportable: the dataset contains customer contact information, public links were enabled, and an external download occurred. The first action is not to independently remediate, notify customers, or change classification. Those steps may be part of the formal response, but they should be coordinated by security, privacy, legal, or governance teams according to policy. Reporting promptly also helps preserve evidence and start containment without compromising the investigation.

  • Deleting evidence may remove useful forensic details and should not replace formal incident reporting.
  • Customer notification is usually handled by authorized privacy or legal teams after assessment.
  • Reclassification would not fix the exposure and would conflict with the stated confidential classification.

Question 10

Topic: Data Governance

A sales analyst built a monthly KPI report by manually combining three CSV exports and applying filters requested in email threads. The analyst is moving to another team, and internal audit needs to understand how each metric was produced. Which approach best reduces the risk to repeatability, auditability, and handoff?

Options:

  • A. Add more KPI visuals for executive users.

  • B. Export the final report as a locked spreadsheet.

  • C. Create a lineage and transformation runbook for the report.

  • D. Increase the report refresh frequency to weekly.

Best answer: C

Explanation: Missing documentation creates governance risk when a report depends on manual source selection, emailed requirements, undocumented filters, or analyst-specific knowledge. A lineage and transformation runbook captures where the data came from, how it was changed, which business rules were applied, who owns each step, and how to reproduce the output. That supports audit review because metric logic can be traced, and it supports handoff because another analyst can rerun or validate the process without guessing. Improving delivery speed, locking outputs, or enhancing visuals may help other needs, but they do not explain how the metrics were produced.

  • Refresh frequency addresses timeliness, not the missing process details needed to reproduce or audit the KPI logic.
  • Locked spreadsheet protects a final artifact but does not document source lineage or transformation steps.
  • More visuals improves presentation but leaves the underlying metric definitions and filters unclear.

Continue with full practice

Use the CompTIA Data+ DA0-002 Practice Test page for the full IT Mastery practice bank, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.

Try CompTIA Data+ DA0-002 on Web View CompTIA Data+ DA0-002 Practice Test

Free review resource

Read the CompTIA Data+ DA0-002 Cheat Sheet on Tech Exam Lexicon, then return to IT Mastery for timed practice.

Revised on Thursday, May 28, 2026