C100DEV Data Modeling Practice Question
What is the primary risk of using the 'Linking Pattern' improperly?
⚠ Common exam trap
Candidates often believe normalizing data completely into separate collections avoids all performance issues, failing to realize that excessive linking hurts throughput.
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 reduces read performance due to increased $lookup overhead.
The primary risk is creating too many 'joins' (lookups) in the application, which leads to slow performance. When you link data across collections, the database must perform extra work to resolve these references. If done too frequently, especially in high-traffic read paths, it creates significant latency and increases the load on the database, which directly undermines the performance benefits usually associated with MongoDB's document-based architecture.
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 causes data inconsistency.
Why it's wrong here
Linking does not inherently cause inconsistency; it simply shifts the burden of maintaining relationships to the application layer. While application-level consistency is harder to manage than database-level constraints, inconsistency is a result of poor application logic, not the linking pattern itself. It is a valid, though complex, modeling technique.
- ✓
It reduces read performance due to increased $lookup overhead.
Why this is correct
Every $lookup requires the database to scan an index or collection to resolve the reference, which is significantly slower than reading an embedded document. Frequent lookups lead to high latency. This is the main performance trade-off developers make when they choose to normalize data across collections instead of embedding it.
- ✗
It forces the use of fixed schema documents.
Why it's wrong here
Linking actually allows for greater schema flexibility because the referenced documents are decoupled. You can have different shapes of documents in the referenced collection without affecting the primary collection. This pattern is not about forcing schemas but about separating concerns, making it quite useful for modular, evolving application designs.
- ✗
It prevents the use of secondary indexes on the collection.
Why it's wrong here
Secondary indexes work perfectly fine in a linked schema. In fact, they are often required to make the lookups performant. Saying that linking prevents indexing is simply wrong; without indexes on the referenced IDs, the lookups would be even slower, making indexing essential for a functioning linked data model.
Visual reference
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.