C100DBA Philosophy and Features Practice Question
Which TWO of the following are benefits of the MongoDB 'document' model over the traditional 'relational' model?
⚠ Common exam trap
Candidates occasionally select relational benefits like strict ACID guarantees across distributed nodes by default, missing that document models prioritize hierarchical structures and reduced joins.
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
✓
Built-in support for complex, hierarchical data structures.
The document model excels in developer agility and data modeling flexibility. By grouping related data, it optimizes for common access patterns, which enhances read performance by reducing the need for joins. This approach aligns with modern programming paradigms where objects are the primary unit of development, allowing for faster iterations and easier maintenance compared to relational models that require complex schema changes and manual data normalization across multiple tables.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Built-in support for complex, hierarchical data structures.
Why this is correct
The document model supports nesting documents and arrays natively. Relational databases often struggle with this, requiring either many-to-many tables or flat structures that do not accurately represent the data. This hierarchy makes it easier to model real-world data and improves query performance for read-heavy object retrieval.
- ✗
Requirement for strict normalization of all data.
Why it's wrong here
Normalization is the hallmark of relational databases. In MongoDB, denormalization is often encouraged to optimize for performance. Requiring normalization would force developers to use multiple joins, which undermines the primary performance and simplicity benefits of the document model's design philosophy for high-concurrency, web-scale applications.
- ✓
Reduced need for expensive JOIN operations.
Why this is correct
By embedding related data, the application can often satisfy queries with a single document fetch. This eliminates the CPU and memory-intensive join operations required in relational databases. While joins are possible, the design goal is to structure data in a way that minimizes their necessity.
- ✗
Guaranteed consistency through mandatory schema migrations.
Why it's wrong here
Schema migrations are a significant pain point in relational databases. MongoDB's schema-less model eliminates the need for these migrations, which is a major benefit for developer productivity. Suggesting that mandatory migrations are a benefit is factually incorrect as they represent administrative overhead and potential downtime.
- ✗
Automatic translation of SQL queries to BSON.
Why it's wrong here
MongoDB does not automatically translate SQL to BSON. While some middleware tools exist, the database natively uses the MongoDB Query Language (MQL). This is not a benefit of the model itself; rather, it represents a fundamental difference in the query interfaces between the two database types.
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.