C100DEV Aggregation Framework Practice Question
What is the primary benefit of using an index with the $match stage at the beginning of an aggregation pipeline?
⚠ Common exam trap
Test-takers often place $match stages later in the aggregation pipeline, missing the performance benefits of filtering early with indexes.
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 enables the engine to quickly select a subset of documents.
When an aggregation pipeline starts with a $match stage, MongoDB can utilize indexes to filter the collection before processing any further stages. This drastically reduces the number of documents loaded into memory, which is the most effective way to optimize pipeline performance. Without index usage, MongoDB must perform a collection scan, which is significantly slower as the dataset grows, making index usage essential for production 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.
- ✗
It guarantees that the output documents are sorted.
Why it's wrong here
$match does not perform sorting. Sorting is handled by the $sort stage. Relying on an index to implicitly provide order for $match is not a reliable practice for aggregation results, as indexes are used for filtering, not for guaranteeing the final order of documents returned by the pipeline.
- ✗
It allows the pipeline to bypass the 100MB RAM limit.
Why it's wrong here
Using an index does not change the memory constraints of the aggregation framework. The 100MB RAM limit applies to the intermediate stages of an aggregation operation. While filtering reduces data volume and lowers memory usage, it does not remove the fundamental architectural limits imposed on the pipeline execution.
- ✓
It enables the engine to quickly select a subset of documents.
Why this is correct
Indexes allow the database to locate relevant documents quickly, avoiding the need to perform a full collection scan. By using an index in the initial $match stage, the engine processes fewer documents, significantly improving performance and reducing resource consumption for every subsequent stage of the aggregation pipeline.
- ✗
It automatically formats the output fields.
Why it's wrong here
$match is purely a filtering operator. It has no role in the formatting, renaming, or projection of fields. Field manipulation is exclusively the responsibility of the $project stage. Therefore, index usage in $match provides performance benefits, not structural or formatting changes to the documents being processed.
About these practice questions
This C100DEV question is part of Courseiva's 259-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 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.