C100DBA Philosophy and Features Practice Question
Which design principle should guide the decision between embedding and referencing?
⚠ Common exam trap
Students frequently rely on relational normalization rules instead of analyzing specific application workloads when deciding how to structure their MongoDB data.
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
✓
Model data based on the application's read and write patterns.
The primary principle for data modeling in MongoDB is the 'access pattern.' You should model data to match how your application queries it. If data is almost always retrieved together, it should be embedded. If the data is accessed independently or is extremely large, it should be referenced. This ensures that the system remains performant by minimizing the number of disk reads and network round-trips required to serve requests.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Always embed to prevent any possibility of data duplication.
Why it's wrong here
Embedding often results in some data duplication. This is a common and acceptable trade-off in MongoDB. The goal is to optimize for the access pattern, not to strictly avoid duplication. If you strictly avoid duplication, you would be forced into a relational design, which causes performance issues.
- ✗
Always reference to keep the database size as small as possible.
Why it's wrong here
While referencing keeps document size smaller, it frequently results in multiple queries to assemble a single object. This significantly increases latency and puts unnecessary strain on the database engine. Performance, not disk space, is usually the more important metric for modern high-performance application requirements.
- ✓
Model data based on the application's read and write patterns.
Why this is correct
The access pattern dictates the optimal schema. Embedding is preferred for data that is read together to minimize I/O, while referencing is better for large or shared data. This approach puts the application's performance needs first, ensuring that the database schema is an asset rather than a bottleneck.
- ✗
Use embedding for all data to ensure ACID compliance.
Why it's wrong here
ACID compliance is a feature of the MongoDB storage engine and can be achieved with both embedded and referenced data models. Embedding does not inherently provide better ACID compliance; it only provides atomic updates to the document, which is just one aspect of overall transactional data integrity.
About these practice questions
This C100DBA question is part of Courseiva's 222-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 C100DBA 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 C100DBA exam.