DA0-002 Data Concepts and Environments Practice Question
A data engineer is designing storage for a fraud detection system that ingests millions of transaction events per second. The system must store each event with its timestamp and support fast writes without predefined schema enforcement, while allowing later analytical queries over semi-structured payloads. Which storage approach best fits these requirements?
⚠ Common exam trap
The trap here is assuming that any database capable of analytical queries must be a columnar warehouse, overlooking that schema-on-read NoSQL stores can also support analytics over semi-structured 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
✓
A document-oriented NoSQL database with schema-on-read
The requirements combine high-velocity ingestion, absence of predefined schema, and support for semi-structured payloads with later analytical querying. Document-oriented NoSQL databases provide schema-on-read flexibility and horizontal write scalability that match these needs. Relational, columnar, and graph systems each impose constraints or optimizations that conflict with one or more of the stated requirements.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A document-oriented NoSQL database with schema-on-read
Why this is correct
Document-oriented NoSQL databases accept semi-structured payloads without predefined schema enforcement, support high write throughput through horizontal scaling, and apply schema-on-read during queries. These characteristics align with ingesting millions of transaction events per second and later analyzing flexible JSON-like documents, making this approach the best fit.
- ✗
A relational OLTP database with third normal form tables
Why it's wrong here
A normalized OLTP relational database enforces rigid schemas and is designed for transactional integrity rather than millions of semi-structured writes per second. Ingesting variable payloads would require constant schema migrations or transformation, creating bottlenecks. This approach does not satisfy the high-velocity, schema-flexible requirements of the fraud detection system.
- ✗
A graph database optimized for relationship traversal
Why it's wrong here
Graph databases excel at traversing relationships between entities, such as detecting fraud rings, but they are not optimized for ingesting millions of independent event documents per second with flexible schemas. The scenario emphasizes high-volume event storage and semi-structured payloads rather than relationship traversal, so a graph database is not the best fit.
- ✗
A columnar data warehouse with strict schema-on-write
Why it's wrong here
Columnar warehouses excel at analytical queries but typically enforce schema-on-write and are optimized for batch or micro-batch loads rather than millions of writes per second. Strict schema enforcement would reject or require transformation of semi-structured payloads before ingestion, conflicting with the need for flexible, high-velocity writes in this fraud detection scenario.
Go deeper
Related to this question
About these practice questions
Courseiva writes every DA0-002 question from scratch — 1,004 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.