DA0-002 Data Concepts and Environments Practice Question
A retail company stores customer transaction data in a relational database. They want to analyze purchasing patterns over time. Which type of data structure best supports this analysis?
⚠ Common exam trap
Watch out — candidates often confuse 'analyzing purchasing patterns over time' with needing a graph database for relationships, but the key requirement is structured time-series aggregation, which is a core strength of relational tables, not graph or NoSQL stores.
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
✓
Relational table
A relational table is the correct choice because it organizes transaction data into structured rows and columns with defined schemas, enabling efficient SQL-based queries for time-series analysis (e.g., aggregating purchases by date, customer, or product). The relational model supports ACID transactions and joins across related tables (e.g., customers, products, transactions), which is essential for analyzing purchasing patterns over time while maintaining data integrity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Relational table
Why this is correct
A relational table stores transactions as rows with typed columns, so SQL aggregation and time-series grouping can reveal purchasing trends. Its fixed schema and join support satisfy the requirement to analyse historical transaction records over time, which non-relational or unstructured stores handle less directly.
- ✗
Graph database
Why it's wrong here
Graph databases model relationships and traversal between entities such as social networks or fraud rings, not time-ordered aggregation of transactions. It is tempting because purchase patterns involve connections between customers and products, but temporal trend analysis needs the columnar storage and aggregation a data warehouse provides.
- ✗
Document store
Why it's wrong here
Document stores hold semi-structured JSON-like records with flexible schemas, offering no native columnar aggregation or time-series functions. It is tempting because transaction records could be stored as documents, but analysing purchasing patterns over time requires the structured summarisation and query performance of a data warehouse.
- ✗
Key-value store
Why it's wrong here
Key-value stores retrieve records by a single key with no query engine for joins, grouping or temporal aggregation. It is tempting because they scale cheaply for high-volume lookups, but analysing purchasing patterns over time demands the columnar storage, SQL aggregation and historical modelling a data warehouse supplies.
Go deeper
Related to this question
About these practice questions
This DA0-002 question is part of Courseiva's 1,004-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.