C100DEV Data Modeling Practice Question
Which of the following describes the 'Extended Reference' pattern and its primary use case?
⚠ Common exam trap
Candidates confuse the Extended Reference pattern with complete data duplication or embedding, forgetting that it only copies a select few frequently accessed fields.
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
✓
Copying frequently accessed fields to a referenced document to minimize joins.
The Extended Reference pattern involves copying frequently accessed fields from a referenced document into the current document. This eliminates the need for costly $lookup operations during read queries. It is a vital pattern for high-performance applications where latency is critical, as it trades a small amount of data redundancy for significant gains in read speed by enabling single-document retrieval for complex data views.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Embedding all child documents to ensure total data atomicity.
Why it's wrong here
Embedding everything for atomicity is not the Extended Reference pattern; it is simple embedding. While embedding provides atomicity, it is often not suitable for large or unbounded relationships. The Extended Reference pattern explicitly focuses on copying only specific, frequently used fields to optimize reads without embedding the entire record.
- ✗
Storing the entire child document inside the parent for faster retrieval.
Why it's wrong here
Storing the entire child document is just standard embedding. The Extended Reference pattern is distinct because it specifically copies only a subset of fields from a referenced document into the parent, maintaining the separation of data while providing the convenience of having common fields available for immediate access.
- ✓
Copying frequently accessed fields to a referenced document to minimize joins.
Why this is correct
This pattern reduces the need for expensive $lookup operations. By duplicating frequently used data fields from the 'many' side into the parent document, you can fulfill most read requests using a single query. This improves latency and reduces server load, which is a key goal in high-performance MongoDB data modeling.
- ✗
Using an array of document IDs to link parent and child documents.
Why it's wrong here
Storing an array of IDs is standard referencing. While this is necessary for linking, it does not provide the performance benefits of the Extended Reference pattern. Standard referencing still requires an application-side or aggregation-based join, whereas the Extended Reference pattern allows you to bypass that need for most common operations.
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.