C100DBA Philosophy and Features Practice Question
Which design principle explains why MongoDB uses a document-oriented model instead of a rigid tabular schema?
⚠ Common exam trap
Candidates often confuse the document model with simple performance optimization, failing to recognize that the primary driver is the alignment with object-oriented application structures to improve developer productivity and schema flexibility.
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
✓
Aligning data storage with object-oriented application models.
MongoDB utilizes a document model to align data structures with how applications represent objects, promoting developer productivity and flexibility. By allowing nested structures, developers avoid complex joins required in relational systems, which significantly improves read performance for related data. This philosophy enables schemas to evolve organically as application requirements change, supporting agile development cycles where modifying a table's structure across millions of rows would otherwise impose significant operational overhead or downtime.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Normalization of data to reduce storage footprints.
Why it's wrong here
Normalization is a relational database principle aimed at reducing redundancy. MongoDB encourages denormalization, where related data is often embedded within a single document to optimize query patterns and minimize the need for server-side joins, which are computationally expensive compared to direct document retrieval.
- ✗
Strict enforcement of data types via ACID compliance.
Why it's wrong here
While MongoDB supports multi-document ACID transactions, its primary philosophy is dynamic schema flexibility. Strict enforcement is a trait of relational databases. MongoDB's document model allows for polymorphic data, where documents in the same collection can have different fields, unlike rigid tabular schemas.
- ✓
Aligning data storage with object-oriented application models.
Why this is correct
The document model maps naturally to objects in modern programming languages. By storing data as BSON documents, MongoDB removes the impedance mismatch found in ORM layers. This allows developers to work with native data structures, simplifying code logic and accelerating the mapping between database and application.
- ✗
Ensuring all related data is stored in separate collections.
Why it's wrong here
Storing related data in separate collections contradicts the document-oriented design, which promotes embedding related information. While referencing is supported, the core philosophy emphasizes capturing context within a single document to ensure that related data is retrieved in a single, efficient disk I/O operation.
About these practice questions
Courseiva writes every C100DBA question from scratch — 222 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 MongoDB exam blueprint
This C100DBA practice question is part of Courseiva's free MongoDB 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 C100DBA exam.