DA0-002 Data Concepts and Environments Practice Question
A data engineer is designing a schema for a new application. The application will store user profiles with fields such as UserID, Email, and SignupDate. The team expects the user base to grow rapidly, and the schema may evolve to include new profile attributes like phone number or social media handles. They want to minimize downtime and avoid complex migrations when adding fields. Which data model should the engineer choose?
⚠ Common exam trap
The trap here is assuming that a relational database's structured schema is always preferable, ignoring the need for frequent schema changes without downtime.
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
✓
Document
A document database provides schema flexibility by storing each user profile as a self-contained document, allowing new attributes to be added without global schema changes or downtime. Relational databases require migrations, key-value stores lack query flexibility, and graph databases are optimized for relationships rather than evolving profile attributes.
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
Why it's wrong here
Relational databases store data in tables with a fixed schema defined by columns and data types. Adding a new attribute like a phone number requires an ALTER TABLE statement, which can lock the table and cause downtime in large systems. While relational models offer strong consistency, they do not provide the schema flexibility needed for rapidly evolving profile attributes.
- ✗
Graph
Why it's wrong here
Graph databases excel at managing complex relationships between entities, such as social networks or recommendation engines. While user profiles could be nodes in a graph, the primary requirement here is flexible schema evolution for profile attributes, not traversing deep relationships. Using a graph database would add unnecessary complexity and overhead for a straightforward profile storage use case.
- ✗
Key-value
Why it's wrong here
Key-value stores map unique keys to opaque values, offering extremely fast lookups but no support for querying by attributes or maintaining relationships. Storing user profiles as key-value pairs would make it difficult to retrieve users by email or filter by signup date. The model lacks the rich querying and indexing capabilities needed for profile management.
- ✓
Document
Why this is correct
Document databases store data in flexible, JSON-like documents where each record can have its own structure. New attributes such as phone number or social media handles can be added to individual documents without altering a global schema or performing migrations. This flexibility aligns perfectly with the requirement to minimize downtime and accommodate evolving user profiles.
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 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.