CompTIA DA0-002 Practice Test 2026

Explanation:
The document contains key metric names and the standardized calculation rules used across the company. This is a classic data dictionary, which defines business terms, metrics, data types, and calculation logic. It ensures consistency in reporting and analysis across teams.

Correct Option:

A. Data dictionary
A data dictionary provides definitions, formats, and calculation standards for data elements and metrics.

It serves as a reference for analysts to understand what each metric means and how it should be computed.

This matches "names of key metrics and the standard for how those metrics are calculated."

Incorrect Options:

B. Data explainability report –
This refers to documentation that helps users understand model predictions or data transformations (e.g., in AI/ML). Not primarily focused on standardizing metric calculations.

C. Data lineage –
Data lineage tracks the origin, movement, and transformations of data from source to destination. It shows where data came from, not how a metric is defined or calculated.

D. Data flow diagram –
A DFD visually maps how data moves between processes, systems, or storage. It shows flow and processing steps, not definitions or calculation standards for metrics.

Reference:
CompTIA Data+ (DA0-002) Exam Objectives Section 1.1 – "Define data concepts," including data dictionaries as tools for documenting metadata, definitions, and business rules. Also covered in data governance and data management best practices.

Explanation:

✅ Why B is Correct

The issue described:
✅ Users are satisfied with support quality
❌ Users complain about long resolution times
🎯 Manager wants to improve the support process

To improve a process, managers track performance metrics.

📌 KPI (Key Performance Indicator)
A KPI is a measurable value used to evaluate how effectively a process is performing.

For support teams, common KPIs include:
⏱️ Average resolution time
⏳ First response time
📈 Ticket backlog
✅ SLA compliance rate

By reviewing KPIs, the manager can:
Identify bottlenecks
Measure delays
Set improvement targets
Monitor process efficiency

❌ Why the Other Options Are Wrong

A. Infographic
Visual communication tool
Presents information attractively
Not used for operational process evaluation

C. Survey
Collects user opinions and feedback
The issue is already known (wait times)
Does not measure process performance

D. UAT (User Acceptance Testing)
Used before system/software launch
Ensures product meets user requirements
Not for improving ongoing support operations

📘 CompTIA Data+ Concept Tested
Data-Driven Decision Making — Performance Monitoring

Tool | Purpose
KPI | Measure process performance and efficiency
Survey | Collect user feedback
Infographic | Visual storytelling
UAT | Pre-release product validation

📚 References
CompTIA Data+ (DA0-002) Objective:
3.3 Given a scenario, apply data-driven decision-making concepts
IT Service Management (ITSM) Performance Metrics
KPI Best Practices in Process Improvement

Explanation:
The problem is that the dashboard shows weekly data but has not updated for several weeks. The best way to confirm that data is current is to proactively check freshness. Setting up a monitoring alert automates this verification, notifying the analyst when data is stale or updates fail.

Correct Option:

A. Setting up a monitoring alert that checks on data freshness
Monitoring alerts can track the last refresh timestamp of the data source or ETL job.

If data hasn't updated within expected cadence (e.g., weekly), an alert triggers.

This provides ongoing confirmation or early warning, not just a one-time check.

Incorrect Options:

B. Working with a DBA on query optimization –
Query optimization improves performance (speed), not data freshness. It does not help confirm whether data is current or detect stale data.

C. Validating that proper data sources are being used –
This checks data correctness (right source), not timeliness. Even with correct sources, the data may still be stale due to update failures.

D. Removing all filters from the dashboard –
Removing filters shows more rows but does not verify if those rows are recent. It masks the underlying freshness issue rather than diagnosing it.

Reference:
CompTIA Data+ (DA0-002) Exam Objectives Section 4.3 – "Given a scenario, maintain the reporting and dashboard lifecycle," including monitoring data freshness and setting up alerts for ETL job failures or delayed updates. Also aligns with data governance best practices.

Explanation:

When gathering requirements for a report or dashboard, stakeholders typically provide input on the content and look and feel (the what and how it should look). However, they often forget to specify the logistics (the how and when).

The team has provided:

Specific data points: Content — what data to show
Color branding: Design — how it should look
Labels and terminology: Design and user experience — how information should be phrased
Suggested charts and tables: Visualization — how to present the data

The missing piece is how this report will be delivered to them.

Delivery Method
Delivery method includes questions such as:

Should this be a static PDF emailed every Monday morning?
Should it be a live, interactive dashboard on a web portal that users can refresh themselves?
Should it be an Excel file placed into a shared drive?
Should it be embedded in a company presentation?

Without knowing the delivery method, the analyst cannot finalize the technical specifications. For example, a PDF cannot support interactive slicers, while a live dashboard requires hosting infrastructure such as a server or BI platform.

Analysis of Incorrect Options

A. Source validation
Why it's wrong: Source validation refers to confirming that the data comes from a trusted and accurate source. While this is an important part of an analyst's work, it is a technical quality assurance activity rather than a requirement that stakeholders normally specify. Stakeholders typically assume the data source is already valid and reliable.

B. Design elements
Why it's wrong: The team already specified several design elements. Color branding, labels, and suggested charts are all part of the report’s visual and user interface design. Therefore, design is not missing.

D. Report type
Why it's wrong: The report type, such as summary, trend analysis, operational, or compliance reporting, is often implied by the combination of data points and suggested charts. The provided information already suggests a business review report. The delivery method is a more critical missing requirement.

Reference:
CompTIA Data+ Domain 5.0 (Data-Driven Decision Making)

Objective 5.1
Explain the importance of having a framework for data-driven decisions.

Objective 5.2
Given a scenario, design a reporting and visualization solution to meet stakeholder needs. Requirement gathering includes determining not only what data to show, but also how and where the report will be delivered, including distribution method, format, and schedule.

Explanation:

A fact table is a central table in a star or snowflake schema within a data warehouse. It primarily stores:
Foreign keys (relational keys) referencing dimension tables.
Quantitative data or measures, such as sales revenue, quantity sold, or hours worked.
Fact tables provide the numeric values analysts aggregate (sum, average, min/max) during analysis. They are designed for fast retrieval and aggregation.
This matches the CompTIA Data+ Domain 1.4 objective, which covers data structures and environments used for analytics.


Incorrect Answer Analysis

Graph: Graph databases store data as nodes and edges, often used for network relationships or social graph analysis. They do not hold relational keys and numeric measures in the same way a fact table does.
Dimensional: This term usually refers to dimension tables, which store descriptive (categorical) data such as customer names, regions, or product categories. They rarely hold numeric measures—mainly descriptive attributes.
Transactional: Transactional tables store individual events or transactions (like each purchase record). While they do contain data, they are optimized for processing transactions, not for analytical aggregations like a fact table.

Key Concepts and Terminology

Fact Table: A table containing measures (quantitative data) and keys to dimension tables.
Dimension Table: A table containing descriptive or categorical attributes to give context to measures.
Star Schema: A database schema where a central fact table connects to multiple dimension tables.
Foreign Key: A column in one table linking to a primary key in another, enabling relational joins.
Measures vs. Attributes: Measures are numeric and aggregatable; attributes describe or categorize.

Real-World Application

In a sales data warehouse:
The fact table holds Order_ID, Customer_ID, Product_ID, Date_ID, along with numeric measures like Quantity_Sold, Unit_Price, and Total_Revenue.
Dimension tables hold descriptive data like customer demographics, product descriptions, or calendar information.
Analysts can then sum or average these measures by joining the fact table to dimension tables.

References and Resources

CompTIA Data+ (DA0-002) Exam Objectives: Domain 1.4 (data structures for analytics).
Kimball & Ross, The Data Warehouse Toolkit — foundational book on fact and dimension tables.
Microsoft, Snowflake, AWS Redshift documentation on data warehouse schemas.

Common Mistakes

Confusing dimension tables (descriptive data) with fact tables (numeric measures).
Assuming transactional tables automatically equal fact tables. Transactional tables capture events but aren’t structured for analysis like fact tables.
Thinking graph tables are part of standard relational warehousing—they are a different data model altogether.

Domain Cross-Reference

Domain 1: Data Concepts and Environments (data structures for analytics).
Domain 3: Data Analysis and Visualization (aggregating and summarizing measures from fact tables).

Summary

The correct answer is Fact Table (A) because it holds both the relational keys linking to dimensions and the numeric measures used in analysis. Dimension tables hold descriptive data, transactional tables store event-level records, and graph databases store nodes/edges—not numeric measures tied to relational keys.

Explanation:

Question Restatement

This question asks: When using an aggregate function like SUM() in SQL, how can you correctly group and retrieve non-aggregated columns to avoid an error?

Correct Answer Justification — Why B Is Correct

In SQL, when you include an aggregate function like SUM(income) in a SELECT statement alongside non-aggregated columns (firstName, lastName), you must use a GROUP BY clause to tell the database how to group the rows before aggregation. Without GROUP BY, SQL does not know how to combine multiple rows for each person.

The corrected code:

SELECT firstName, lastName, SUM(income) FROM companyRoster GROUP BY firstName, lastName ORDER BY lastName, SUM(income);

This syntax correctly groups income by each first and last name, then allows sorting or ordering by the aggregated values. This is exactly what Option B specifies — adding GROUP BY firstName, lastName fixes the error.

Incorrect Answer Analysis

A. HAVING SUM(income) > 10000000: HAVING is used to filter after aggregation, but it does not resolve the requirement to group non-aggregated columns. You still need a GROUP BY even if you use HAVING.

C. ORDER BY firstName, income: ORDER BY alone does not fix the aggregation issue. The original error is not about sorting—it’s about missing GROUP BY.

D. SELECT firstName, lastName, SUM(income) FROM companyRoster: Leaving it as-is still produces an error because of mixing aggregated and non-aggregated columns without a GROUP BY.

Key Concepts and Terminology

Aggregate Function: A function (SUM, COUNT, AVG, MAX, MIN) that returns a single value from multiple rows.

GROUP BY Clause: Groups rows sharing values of specified columns into summary rows, one for each unique group. Required when mixing aggregates and non-aggregates.

HAVING Clause: Filters groups after aggregation (similar to WHERE but for grouped data).

ORDER BY Clause: Sorts the returned rows; does not affect grouping or aggregation.

Real-World Application

If you’re analyzing company payroll, you might want to see total income per employee. Using GROUP BY firstName, lastName aggregates multiple paychecks or commissions under each employee’s name. Without it, SQL cannot compute a single SUM per employee and throws an error.

References and Resources

CompTIA Data+ (DA0-002) Exam Objectives: Domain 2.1 (data manipulation using SQL).
W3Schools SQL GROUP BY documentation.
ANSI SQL standard on aggregate functions.

Common Mistakes

Trying to mix aggregate and non-aggregate columns without using GROUP BY.
Confusing HAVING (filter groups) with WHERE (filter rows before grouping).
Using SORT BY instead of ORDER BY—SQL uses ORDER BY as the correct syntax.

Domain Cross-Reference

Domain 2: Data Mining and Manipulation (performing aggregations and grouping).
Domain 3: Data Analysis and Visualization (summarizing and displaying data properly).

Summary

The SQL fails because it mixes aggregated and non-aggregated columns without grouping. Adding GROUP BY firstName, lastName (Option B) fixes the issue, letting SQL correctly aggregate income per person. HAVING filters groups after aggregation but does not replace GROUP BY. ORDER BY only sorts results and does not resolve the aggregation error.

Explanation:

Why C is Correct
The key clues:

The analyst reset their company password
A recurring analysis connects automatically to a database
Later error: “Log-in failed for user”

Most automated reports, dashboards, and scheduled analyses store saved credentials.

If the analyst changed their password but did not update the stored credentials in:

the reporting tool
scheduled task
database connection string

➡️ The system will keep trying the old password
➡️ Login will fail

This is the most common cause of this scenario.

Why the Other Options Are Wrong

A. The company changed its database authentication method
This would affect many users and systems
Typically involves migration notices and system-wide issues
Not triggered by a single user password reset

B. The password expiration process locked the account
The analyst already reset the password
Account lockouts occur after repeated failed attempts
The scenario points to credential mismatch, not lockout

D. The company is experiencing issues with password replication
Rare and enterprise-infrastructure specific
Would affect multiple systems and users
No evidence of widespread authentication problems

CompTIA Data+ Concept Tested
Data Operations — Access & Credential Management

Common operational issue:

When passwords change, all automated processes using stored credentials must be updated.

Examples:

BI dashboards
Scheduled ETL jobs
Database connectors
API integrations

References

CompTIA Data+ (DA0-002) Objective:
2.2 Given a scenario, apply data governance and controls
(Access management and credential handling)

Database authentication & credential storage best practices

Explanation:

The dashboard:
Displays 7 years of data
Pulls from a database containing 30 years of data
Is running slowly

The performance issue is likely caused by retrieving more data than necessary.

Best solution:
Limit queries to only the data needed

Filtering:
Reduces data volume
Speeds up query execution
Lowers memory and processing load
Improves dashboard responsiveness

This is a core data performance optimization technique.

❌ Why the Other Options Are Incorrect

A. Performing a code review
Useful for logic or syntax issues
Not the primary cause of slow performance here

B. Checking network connectivity
Network issues cause connection failures or latency
Not excessive data processing delays

D. Adding more RAM and rerunning
Hardware upgrade is costly
Treats the symptom, not the root cause
Query optimization should come first

📘 References (CompTIA Data+ DA0-002 Concepts)
Relevant domains:
Query optimization
Dashboard performance tuning
Data retrieval efficiency

Key concept:
Improve performance by minimizing unnecessary data retrieval.

Question

A data analyst is analyzing the following dataset:

Transaction Date

Quantity Item

Item Price

Example rows:
12/12/12 — 11 — USB Cords — 9.99
11/11/11 — 3 — Charging Block — 8.89
10/10/10 — 5 — Headphones — 50.15


Which of the following methods should the analyst use to determine the total cost for each transaction?

Options:
A. Parsing
B. Scaling
C. Compressing
D. Deriving

Correct Answer: D. Deriving

Question Restatement

This question asks: If you have quantity and item price per transaction, what method do you use to create a new column (total cost) from existing columns?

Correct Answer Justification — Why D Is Correct

Deriving refers to creating a new variable or field from one or more existing variables. In this case:
Existing fields: Quantity and Item Price.
Derived field: Total Cost = Quantity × Item Price.
This is a textbook example of a calculated or derived field — you’re not cleaning or scaling data, you’re computing a new metric from existing data.

CompTIA Data+ Domain Alignment:

Domain 2.3 (Data Manipulation): Using transformations, derived fields, and calculated metrics to enrich datasets.

Incorrect Answer Analysis

Parsing: Breaking data into smaller parts or extracting specific elements from a string (like splitting “12/12/12” into month, day, year). Parsing is not about performing calculations between fields.

Scaling: Adjusting data to a different magnitude or range (like normalization or standardization for machine learning). Scaling changes existing values, not creating new ones.

Compressing: Reducing the size of data for storage efficiency. This has nothing to do with creating new fields or calculating totals.

Key Concepts and Terminology

Derived Field (or Calculated Column): A new data field created using a formula or expression applied to existing data fields.
Data Transformation: The process of converting, combining, or deriving new variables to make data more useful for analysis.
Parsing: Extracting meaningful components from strings or raw data.
Scaling: Adjusting numbers to a consistent range or unit.

Real-World Application

In a retail analytics scenario, analysts routinely create derived fields such as:
Total Revenue per transaction (Quantity × Price).
Profit Margin (Revenue − Cost).
Customer Lifetime Value (sum of transactions per customer).
This process enriches the dataset and allows for more meaningful metrics and KPIs.

References and Resources

CompTIA Data+ Exam Objectives: Domain 2 (Data Mining and Manipulation).
Data Warehousing & BI Concepts — Derived Columns in ETL tools like Informatica, Talend, or SQL’s calculated columns. Microsoft Power BI / Tableau calculated fields documentation.

Common Mistakes

Thinking parsing applies because of the text columns (dates/items). Parsing is only about breaking text, not multiplying fields.

Mistaking scaling for any numeric change. Scaling changes the magnitude, not the structure.
Overlooking derived fields as a basic data manipulation technique.

Domain Cross-Reference

Domain 2: Data Mining and Manipulation (deriving and transforming fields).
Domain 3: Data Analysis (calculating metrics from existing data).

Summary

The correct answer is D. Deriving because determining the total cost for each transaction requires creating a new metric (Quantity × Item Price) from existing data fields. Parsing, scaling, and compressing don’t create calculated fields.

Explanation:
The requirement includes predefined filters (user-selectable options) and ability to download .csv files. A self-service portal allows users to apply filters and export raw data on demand. Other options either lack interactivity or do not provide direct .csv download capability.

Correct Option:

C. Creating a self-service portal on the company's intranet
A self-service portal can host reporting tools with predefined filter controls (drop-downs, date pickers).

Users can generate customized views and download data in .csv format directly.

It empowers users without requiring repeated engineer intervention for each report.

Incorrect Options:

A. Developing a dynamic dashboard that refreshes daily –
Dashboards are great for visualization but often limit downloads to aggregated data or images, not raw .csv files. Predefined filters may exist, but the primary output is visual, not file-based.

B. Generating a weekly executive summary –
This is a static, scheduled report, not interactive. It lacks predefined filters for user customization and may not provide downloadable .csv data.

D. Building an email template to request ad hoc reports –
This adds manual steps; users request reports, and someone must run and email them. It does not provide immediate self-service filtering or direct .csv download.

Reference:
CompTIA Data+ (DA0-002) Exam Objectives Section 4.2 – “Explain common styles of data visualization and reporting,” including self-service reporting vs. static reports. Also aligns with best practices in business intelligence portals (e.g., Power BI Report Server, Tableau Server with export options).