DA0-002 Data Concepts and Environments Practice Question
A data architect is designing a system to store data for a real-time analytics application. The application requires high-speed ingestion of semi-structured data with flexible schemas, and the ability to query data using SQL-like syntax. The data volume is expected to grow rapidly. Which type of database should the architect choose?
⚠ Common exam trap
The trap here is assuming that a relational database or data warehouse can handle flexible schemas and real-time semi-structured ingestion just because they support SQL.
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
✓
NoSQL document database
A NoSQL document database is the best choice because it handles semi-structured data with flexible schemas, supports high-speed ingestion, and scales horizontally. It often provides SQL-like query capabilities. Relational databases are too rigid, data warehouses are for structured historical data, and graph databases are for relationship-heavy use cases.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
NoSQL document database
Why this is correct
A NoSQL document database stores semi-structured data in flexible, JSON-like documents and supports high-speed ingestion and horizontal scaling. Many document databases also offer SQL-like query languages or APIs. This makes it well-suited for real-time analytics with evolving schemas and large data volumes.
- ✗
Graph database
Why it's wrong here
A graph database is designed to store and query relationships between entities, using nodes and edges. It excels at traversing complex relationships but is not optimized for high-volume semi-structured data ingestion or general SQL-like querying. The scenario does not emphasize relationship-centric queries, so a graph database is not the best fit.
- ✗
Relational database
Why it's wrong here
A relational database enforces a fixed schema and uses structured tables with rows and columns. While it supports SQL, it is not ideal for semi-structured data with flexible schemas because schema changes require migrations. It also may not scale horizontally as easily as NoSQL databases for high-volume, high-speed ingestion.
- ✗
Data warehouse
Why it's wrong here
A data warehouse is optimized for analytical queries on structured, historical data, typically loaded through ETL processes. It is not designed for high-speed ingestion of semi-structured data in real time. While it supports SQL, it lacks the flexibility for rapidly changing schemas and may not handle real-time ingestion efficiently.
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.