DA0-002 Data Concepts and Environments Practice Question
A data architect is designing a schema for a product catalog where each product has a variable number of attributes. Which NoSQL database type is most appropriate?
⚠ Common exam trap
Test-takers frequently confuse 'variable attributes' with 'relationships' and incorrectly choose a graph database, or they assume key-value stores are flexible enough, overlooking the need for queryability on individual attributes.
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 store
A document store (e.g., MongoDB, Couchbase) is the most appropriate choice because it stores data in flexible, self-describing documents (typically JSON or BSON), allowing each product to have a variable number of attributes without requiring a predefined schema. This directly matches the requirement of a product catalog where attributes can differ per product, unlike rigid relational tables that would require complex EAV (Entity-Attribute-Value) patterns or frequent schema migrations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Graph database
Why it's wrong here
A graph database models entities and relationships as nodes and edges, optimising traversal queries such as friend-of-friend; it does not store or query independent variable attributes per product. It is tempting because it handles flexible schemas, but it suits connected data like social or recommendation networks.
- ✓
Document store
Why this is correct
Document stores hold each product as a self-describing JSON-like document, so attributes can vary per item without a fixed schema. This directly satisfies the stem's variable-attribute constraint, unlike columnar or key-value models that require predefined structures. Nested attributes and arrays are queried natively, matching heterogeneous catalog entries.
- ✗
Key-value store
Why it's wrong here
A key-value store retrieves items by a single key and offers no query language for filtering on arbitrary attributes, so variable product attributes cannot be queried efficiently. It is tempting because it handles flexible, schemaless values, but that suits session or cache lookups, not attribute-based catalog searches.
- ✗
Relational database
Why it's wrong here
A relational database requires a fixed schema with predefined columns, so adding per-product attributes needs schema changes or sparse nullable columns, and joins scale poorly. It is tempting because it enforces consistency and supports SQL, which suits structured transactional data rather than variable-attribute catalogs.
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 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.