C100DEV Data Modeling Practice Question
What is the primary benefit of the 'Extended Reference Pattern'?
⚠ Common exam trap
Candidates often assume the pattern is for data integrity or normalization, missing that its primary purpose is performance optimization by minimizing application-level joins.
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
✓
It improves read performance by reducing the need for joins.
The Extended Reference Pattern involves copying a small amount of frequently accessed data from a referenced document into the primary document. This allows the application to retrieve the most critical information in a single read, avoiding a join for the majority of use cases. It optimizes for the common case while still allowing the full referenced document to be fetched only when truly needed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
It completely eliminates the need for any referencing in the database.
Why it's wrong here
This pattern is a hybrid approach, not an elimination of referencing. You still maintain the reference to the full document. Claiming it eliminates referencing is fundamentally incorrect, as the pattern relies on keeping that reference intact to fetch the full object when necessary for deeper operations.
- ✓
It improves read performance by reducing the need for joins.
Why this is correct
By embedding a few key fields from the referenced document, you can often satisfy the user's request without a join. This significantly reduces the overhead of constant $lookup calls, making the application faster and more responsive for the most frequent read operations while keeping the architecture flexible.
- ✗
It allows documents to grow indefinitely without size limits.
Why it's wrong here
The 16MB limit is a hard constraint for all MongoDB documents. This pattern does not change or expand that limit. It is a design choice to optimize data access, and developers must still be mindful of document size when choosing which fields to extend into the primary document.
- ✗
It ensures that all data across all collections remains perfectly synchronized.
Why it's wrong here
This pattern actually introduces a challenge with data synchronization, as the extended fields in the primary document must be updated whenever the source data changes. It does not provide automatic synchronization; rather, it requires careful application-level logic to ensure data consistency between the primary and referenced documents.
About these practice questions
Courseiva writes every C100DEV question from scratch — 259 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 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.