C100DBA Philosophy and Features Practice Question
Why does MongoDB support both embedding and referencing in data modeling?
⚠ Common exam trap
A common mistake is assuming MongoDB forces either strict embedding or strict normalization, ignoring the flexibility required to handle document size limits and relationships.
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
✓
To manage data size limits and complex relationships.
Embedding is ideal for performance when data is accessed together, but referencing is necessary for handling unbounded data, complex relationships, or avoiding document size limits (16MB). By offering both, MongoDB provides the flexibility to choose the right strategy based on the specific cardinality and access frequency of the data, allowing developers to balance performance and storage constraints effectively without forcing a one-size-fits-all architectural approach.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
To support legacy relational database imports.
Why it's wrong here
While referencing can mimic relational joins, it is not primarily for imports. It is a fundamental modeling choice for managing relationships where embedding would result in documents exceeding the 16MB limit or where many-to-many relationships require independent data lifecycle management.
- ✓
To manage data size limits and complex relationships.
Why this is correct
MongoDB documents have a 16MB limit. For large or unbounded datasets, embedding would eventually fail. Referencing allows developers to link documents, maintaining relationships without hitting storage limits or causing data duplication, which is critical for scalable, maintainable application data models.
- ✗
To force developers to use ACID transactions.
Why it's wrong here
Referencing does not mandate the use of ACID transactions. While multi-document transactions can be used with referenced data, the primary purpose of referencing is structural and size-based, not to enforce transactional integrity protocols, which remain an optional feature for application-level data consistency.
- ✗
To eliminate the need for indexes in the database.
Why it's wrong here
Referencing requires indexes on the fields used for lookups to perform well. Without these indexes, referenced queries would require full collection scans, which would degrade performance significantly. Therefore, referencing actually increases the importance of a well-defined indexing strategy for any foreign key fields.
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.