C100DEV Aggregation Framework Practice Question
What is the primary benefit of using $unionWith to combine data from two collections in a single pipeline?
⚠ Common exam trap
Candidates sometimes confuse $unionWith with $lookup, believing $unionWith performs a join between collections, whereas it actually performs a set union by appending results from one collection to another.
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 allows querying multiple collections in one pipeline.
$unionWith allows developers to append results from one collection to another within a single aggregation pipeline. This provides a mechanism for performing multi-collection queries without the overhead of multiple application-level calls. It simplifies data retrieval for scenarios like merging similar data from sharded collections or combining logs from multiple time-based collections, which is a powerful technique for efficient data consolidation and reporting.
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 automatically joins documents based on a common ID.
Why it's wrong here
Joining documents based on an ID is the role of the $lookup operator. $unionWith simply concatenates result sets from different collections, effectively acting like a SQL UNION ALL. It does not perform any matching or merging logic between the documents from the different collections involved.
- ✓
It allows querying multiple collections in one pipeline.
Why this is correct
$unionWith provides a clean, single-pipeline approach to aggregate data from multiple collections. This reduces the latency of network round-trips from the application layer to the database, as the entire data consolidation process is executed on the server, resulting in faster and more efficient query execution.
- ✗
It is faster than $match because it avoids indexes.
Why it's wrong here
Avoiding indexes is never a performance benefit. $unionWith is a processing-heavy stage that requires careful planning. Claiming that avoiding indexes makes a stage faster is fundamentally incorrect, as indexes are the primary tool for achieving efficient data access in any database operation, including aggregation.
- ✗
It replaces the need for a $group stage entirely.
Why it's wrong here
$unionWith is for combining data sets; it has no grouping functionality. To summarize the combined data, you would still need to follow the $unionWith stage with a $group or other aggregation stages. They serve distinct, complementary purposes in the aggregation framework pipeline.
About these practice questions
One of 259 original C100DEV 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 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.