C100DBA Philosophy and Features Practice Question
Which feature of MongoDB allows it to scale horizontally by distributing data across multiple physical servers?
⚠ Common exam trap
Candidates often incorrectly identify 'Replica Sets' as the tool for horizontal scaling. They fail to realize that replica sets primarily provide redundancy, not distribution of data across servers.
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
✓
Sharding to partition data across a cluster.
Sharding is the native MongoDB architecture for horizontal scaling, partitioning data into chunks across a cluster of shards. This strategy addresses storage limitations and throughput bottlenecks that single-node or replica set architectures cannot handle. By distributing read and write operations across multiple nodes, sharding maintains performance as datasets grow to terabyte or petabyte scales, fulfilling the philosophy of providing seamless, scalable infrastructure for global applications.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Vertical scaling via hardware upgrades.
Why it's wrong here
Vertical scaling increases the capacity of a single server, such as adding CPU or RAM. While useful, it has physical limits and diminishing returns. MongoDB is designed to scale out horizontally, which avoids the ceiling of hardware capacity and allows for more cost-effective growth by adding commodity servers.
- ✓
Sharding to partition data across a cluster.
Why this is correct
Sharding is the primary mechanism for horizontal scaling in MongoDB. It segments collections into chunks based on a shard key and distributes them across multiple replica sets. This allows the cluster to handle massive datasets and high throughput by parallelizing operations across the distributed nodes in the cluster.
- ✗
Replica sets for high availability.
Why it's wrong here
Replica sets provide redundancy and high availability through data replication, not horizontal scaling. While they improve read scalability by allowing secondary reads, they do not distribute write workloads across multiple nodes; all writes must still be directed to the primary node, making them insufficient for horizontal growth.
- ✗
Index prefixing for faster query execution.
Why it's wrong here
Index prefixing is an optimization technique used to improve query performance by utilizing the leftmost fields of a compound index. It relates to query tuning and resource efficiency on a single shard, but it provides no mechanism for distributing data or scaling storage capacity across multiple physical servers.
About these practice questions
One of 222 original C100DBA 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 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.