C100DEV Data Modeling Practice Question
Which TWO of the following scenarios are optimal for using the Embedding pattern instead of Referencing?
⚠ Common exam trap
Many candidates choose embedding for unbounded or many-to-many datasets, ignoring MongoDB document size limits and performance degradation risks.
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
✓
A user document containing the user's primary shipping address.
Embedding is preferred when data is accessed together or exhibits a 'contains' relationship, minimizing round trips. It is ideal for one-to-few relationships. Conversely, Referencing is better for large, unbounded datasets or many-to-many relationships. Understanding these trade-offs is critical for MongoDB developers to minimize I/O and maximize the efficiency of read operations, as embedded documents are retrieved in a single read operation by the database engine.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A blog post containing a list of comments that grows indefinitely.
Why it's wrong here
Indefinitely growing lists lead to unbounded arrays, which eventually violate the 16MB document limit. This scenario is a classic example of when to use Referencing, where comments are stored in a separate collection linked by the parent document ID to ensure long-term scalability and document integrity.
- ✓
A user document containing the user's primary shipping address.
Why this is correct
Addresses have a strong 'contains' relationship with the user and are rarely queried independently of the user profile. Embedding them allows the application to retrieve both the user identity and their shipping information in a single read operation, significantly reducing application-side latency and database server load.
- ✗
A product catalog with millions of items linked to various categories.
Why it's wrong here
In a many-to-many scenario, embedding would cause massive data duplication. If a category is renamed, you would need to update every single product document, leading to massive write amplification. Referencing is the superior choice here to maintain data consistency and reduce the overall storage footprint of the database.
- ✓
A movie document embedding the names of its three main cast members.
Why this is correct
The number of main cast members is small and relatively static, fitting the one-to-few pattern perfectly. Embedding them allows the application to display core movie details immediately without needing secondary lookups, providing a much faster user experience for common read operations on the movie details page.
- ✗
A sensor data stream that stores millions of readings per hour.
Why it's wrong here
Storing millions of sensor readings in a single document is physically impossible due to the 16MB limit. This requires high-frequency writes and time-series data modeling, which necessitates storing readings in separate documents or collections to ensure the database can handle the continuous volume of incoming sensor metrics.
About these practice questions
One of 259 original C100DEV practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.