C100DBA Philosophy and Features Practice Question
Exhibit
{
"_id": 1,
"name": "SensorA",
"readings": [22.5, 23.1, 22.8]
}Refer to the exhibit. Which MongoDB philosophy is represented by this document structure?
⚠ Common exam trap
Candidates often misidentify the structure as 'denormalization for normalization's sake' or 'relational mapping,' failing to recognize that embedding is specifically about data locality and reducing expensive join operations.
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
✓
Data locality for optimized retrieval patterns.
This document structure demonstrates the principle of embedding data. Instead of creating a separate collection for sensor readings and joining them via foreign keys, the readings are nested directly within the document. This approach minimizes the need for multi-table joins, which is a key tenet of MongoDB's design to keep data that is accessed together stored together, resulting in faster read performance and simplified application logic for time-series or hierarchical datasets.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Normalization for maximum data consistency.
Why it's wrong here
Normalization involves splitting data into separate entities to reduce redundancy. This document is denormalized because the sensor readings are included within the sensor metadata, prioritizing performance and retrieval efficiency over the strict normalization found in traditional relational database management systems.
- ✓
Data locality for optimized retrieval patterns.
Why this is correct
By embedding the array of readings within the document, MongoDB ensures that all information for 'SensorA' is fetched in a single disk read. This follows the philosophy of data locality, where related information is stored physically together to optimize query performance and reduce latency.
- ✗
Enforcement of a rigid schema using array types.
Why it's wrong here
MongoDB's philosophy centers on schema flexibility, not rigid enforcement. While the array type is used here, the database does not force other documents to contain an array of the same length or data type, highlighting the dynamic nature of the document model over strict relational schemas.
- ✗
The use of an Oplog to track document changes.
Why it's wrong here
The Oplog is an internal MongoDB mechanism for replication, not a feature represented by the document structure itself. While the document will trigger Oplog entries upon update, the structure shown is about data modeling philosophy, not the underlying replication mechanics of the replica set.
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.