C100DEV MongoDB Overview and Document Model Practice Question
When designing a document model, which factor is most important for determining whether to embed or reference data?
⚠ Common exam trap
Candidates often choose based on data relationship size or normalization rules from relational databases, ignoring that MongoDB design must prioritize how the application specifically queries and retrieves the data.
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
✓
The application's data access patterns.
The access pattern—specifically how often data is retrieved and how it is used—is the deciding factor. If data is usually needed together, embedding provides the best read performance. If data is accessed independently or the child data grows without bound, referencing is more appropriate. Aligning the model with access patterns is the core tenet of MongoDB performance optimization and design.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The total number of documents in the collection.
Why it's wrong here
The total number of documents is less important than the access pattern. Even in a collection with millions of documents, embedding is efficient if the application retrieves the data in a single request. Scalability is handled by sharding, not by avoiding embedding based on the total row count.
- ✓
The application's data access patterns.
Why this is correct
Access patterns define the query load. By modeling data to fit how it is queried, you reduce the need for joins and multiple roundtrips. Embedding is ideal for data that is always accessed together, while referencing is better for avoiding large, oversized documents that are rarely fully needed.
- ✗
The memory limit of the database server.
Why it's wrong here
While memory is always a factor, the decision to embed or reference is primarily about query efficiency. Modern hardware can handle large documents, provided the access patterns are optimized. Making design decisions solely based on server memory without considering access behavior will often lead to suboptimal application performance.
- ✗
The complexity of the data's object-oriented relationships.
Why it's wrong here
The document model should be designed based on application usage, not just the object relationships in the code. Mirroring class hierarchies directly can lead to poor performance. Developers must balance logical object structure with the actual performance requirements of the queries that the application will execute most frequently.
About these practice questions
This C100DEV question is part of Courseiva's 259-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 MongoDB exam blueprint
This C100DEV 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 C100DEV exam.