C100DEV Data Modeling Practice Question
When designing a schema for a one-to-many relationship, what is the primary factor in deciding between embedding and referencing?
⚠ Common exam trap
Candidates often choose embedding strictly based on relational foreign key habits or database size limits, ignoring the application's actual read and write access frequency patterns.
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 access pattern and the size of the related data.
The primary factor is the access pattern: how often the data is read and whether the related data is needed together. Embedding is ideal when the child data is frequently accessed with the parent. Referencing is necessary when the child data is large, grows unbounded, or is accessed independently. Choosing the right approach ensures that the application maintains optimal performance by minimizing read latency and avoiding document size limits.
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 document count has minimal impact on the embedding versus referencing decision. MongoDB scales horizontally regardless of collection size. The relationship choice depends specifically on the nature of the data connection and how the application queries that specific data, not on the total number of items stored.
- ✓
The access pattern and the size of the related data.
Why this is correct
Access patterns define whether data is retrieved together, while size constraints prevent hitting the 16MB limit. Balancing these requirements determines if the data should be embedded for performance or referenced for scalability. This is the fundamental trade-off in MongoDB schema design that dictates document structure and query efficiency.
- ✗
The specific version of MongoDB being used by the server.
Why it's wrong here
Schema design principles for embedding versus referencing are consistent across all MongoDB versions. While new features like $lookup have improved referencing, the core decision remains rooted in application data access patterns. Basing design on versioning rather than data relationships is a common mistake that leads to inefficient queries.
- ✗
The hardware specifications of the database server.
Why it's wrong here
While hardware performance is important, schema design should prioritize data access patterns over specific server specs. A well-modeled schema performs better on any hardware. Relying on hardware to compensate for poor data modeling will lead to bottlenecks that no amount of CPU or RAM can fully resolve.
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.