C100DBA Philosophy and Features Practice Question
Which THREE of the following are core tenets of the MongoDB philosophy regarding data modeling?
⚠ Common exam trap
Test-takers often include rigid upfront schema enforcement or mandatory third-normal-form normalization as core tenets, missing the dynamic and query-driven philosophy.
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
✓
Store data that is accessed together in the same document.
MongoDB's data modeling philosophy emphasizes placing data that is accessed together into the same document (embedding). It promotes flexibility by allowing schemas to be dynamic rather than rigid. Furthermore, it encourages developers to design schemas based on the application's specific query patterns, ensuring that the database layout directly supports the most frequent operations, which leads to optimal performance in high-scale environments where relational joins would otherwise create bottlenecks.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Normalize data to the third normal form.
Why it's wrong here
Third normal form is a relational database standard designed to eliminate redundancy. MongoDB often favors denormalization to improve read performance, as joining data across collections is more resource-intensive than retrieving an embedded document that already contains all required related information.
- ✓
Store data that is accessed together in the same document.
Why this is correct
Embedding related data is a foundational practice in MongoDB. By keeping related information together, the application reduces the number of queries needed, effectively minimizing round-trips to the database and increasing throughput by ensuring all necessary data for an operation is available in one place.
- ✓
Allow schemas to evolve dynamically without downtime.
Why this is correct
Dynamic schemas allow for agile development. MongoDB does not enforce structural rigidity, meaning developers can add fields to documents as business requirements change. This avoids the need for heavy schema migration scripts and downtime, which are common pain points in traditional relational database management systems.
- ✗
Always prioritize write consistency over read performance.
Why it's wrong here
MongoDB allows developers to configure consistency levels (e.g., write concern and read concern). It does not force a 'write-first' philosophy at the expense of performance, but rather offers the flexibility to balance these trade-offs based on the specific needs of the application's use case.
- ✓
Design schemas based on application query patterns.
Why this is correct
Unlike relational modeling, which is often data-centric, MongoDB modeling is application-centric. By analyzing how the application reads and writes data, developers can structure documents to perfectly match the expected query results, which ensures the most efficient data access path for the most frequent operations.
About these practice questions
Courseiva writes every C100DBA question from scratch — 222 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 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.