Pipeline execution order matters in MongoDB - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a pipeline in MongoDB aggregation?

A pipeline is a sequence of stages that process data step-by-step, where each stage transforms the data and passes it to the next stage.

beginner

Why does the order of stages in a MongoDB pipeline matter?

Because each stage works on the output of the previous one, changing the order can change the final result or affect performance.

intermediate

What happens if you put a $match stage after a $group stage instead of before?

The $match will filter grouped results instead of raw documents, which can lead to different results and usually less efficient processing.

intermediate

How can placing $project early in the pipeline improve performance?

By selecting only needed fields early, it reduces the amount of data passed through later stages, making processing faster.

beginner

True or False: Changing the order of pipeline stages never affects the output of a MongoDB aggregation.

False. Changing the order can change the output because each stage depends on the previous stage's results.

In a MongoDB aggregation pipeline, which stage should usually come first to reduce data early?

A $match

B $group

C $sort

D $project

Putting $match first filters documents early, reducing data for later stages.

What is the effect of placing $group before $match in a pipeline?

A Projects fields before grouping

B Filters raw documents before grouping

C Sorts documents before grouping

D Groups all documents before filtering

$group before $match means grouping happens on all documents, then filtering happens on grouped results.

Which stage reduces the fields passed to later stages in a pipeline?

A $match

B $project

C $group

D $limit

$project selects specific fields, reducing data size for later stages.

Why is pipeline order important in MongoDB aggregation?

A Because each stage depends on the previous stage's output

B Because stages run in parallel

C Because order affects database indexing

D Because order changes the database schema

Each stage processes the output of the previous stage, so order affects results.

If you want to sort documents after grouping, where should $sort be placed?

A Before $group

B Before $match

C After $group

D At the start of the pipeline

$sort after $group sorts the grouped results.

Explain why the order of stages in a MongoDB aggregation pipeline affects the final output and performance.

Think about how data flows through each stage step-by-step.

Describe a scenario where placing $match after $group would produce a different result than placing it before.

Consider what data each stage sees and processes.

Practice

1. In MongoDB aggregation pipelines, why does the order of stages matter?

easy

A. Because stages run in the order they are written, affecting results and performance

B. Because MongoDB runs all stages in parallel regardless of order

C. Because only the last stage affects the output

D. Because stages can be reordered automatically by MongoDB

Solution

1. Step 1: Understand pipeline execution

   MongoDB executes pipeline stages sequentially in the order they appear.

2. Step 2: Impact of order on results and performance

   Changing the order can change the output and how fast the query runs, especially filtering early helps performance.

3. Final Answer:

   Because stages run in the order they are written, affecting results and performance -> Option A

4. Quick Check:

   Pipeline order affects output and speed [OK]

Hint: Remember: pipeline stages run top to bottom [OK]

Common Mistakes:

• Thinking MongoDB runs stages in parallel
• Believing order does not affect output
• Assuming MongoDB reorders stages automatically

2. Which of the following is the correct syntax to start a MongoDB aggregation pipeline with a filter stage?

easy

A. db.collection.aggregate([{ $match: { status: 'A' } }])

B. db.collection.aggregate({ $match: { status: 'A' } })

C. db.collection.find({ $match: { status: 'A' } })

D. db.collection.aggregate([{ match: { status: 'A' } }])

Solution

1. Step 1: Identify correct aggregation syntax

   The aggregate method takes an array of stages, each stage is an object with a stage operator like $match.

2. Step 2: Check each option

   db.collection.aggregate([{ $match: { status: 'A' } }]) correctly uses an array with $match stage. db.collection.aggregate({ $match: { status: 'A' } }) misses array brackets. db.collection.find({ $match: { status: 'A' } }) uses find() which is not aggregation. db.collection.aggregate([{ match: { status: 'A' } }]) misses $ in $match.

3. Final Answer:

   db.collection.aggregate([{ $match: { status: 'A' } }]) -> Option A

4. Quick Check:

   Aggregation stages are in an array [OK]

Hint: Aggregation stages must be in an array [OK]

Common Mistakes:

• Omitting the array brackets around stages
• Using find() instead of aggregate() for pipelines
• Missing $ in stage operators like $match

3. Given this pipeline:

db.orders.aggregate([
  { $sort: { price: -1 } },
  { $match: { status: 'A' } }
])

What is the main issue with this pipeline?

medium

A. It sorts ascending instead of descending

B. It will cause a syntax error due to stage order

C. It will return no results because $match must come first

D. It filters after sorting, which is less efficient

Solution

1. Step 1: Analyze stage order

   The pipeline sorts all documents first, then filters with $match.

2. Step 2: Understand performance impact

   Filtering first reduces documents early, making sorting faster. Sorting before filtering wastes resources.

3. Final Answer:

   It filters after sorting, which is less efficient -> Option D

4. Quick Check:

   Filter early, then sort for best performance [OK]

Hint: Filter before sort to improve speed [OK]

Common Mistakes:

• Thinking stage order causes syntax errors
• Believing $match must always be first to work
• Confusing sort order direction

4. You wrote this pipeline but it returns an error:

db.sales.aggregate([
  { $group: { _id: "$item", total: { $sum: "$amount" } } },
  { $match: { $gt: ["$total", 100] } }
])

What is the likely cause?

medium

A. The $match stage cannot filter on fields created by $group

B. The $match stage should use $expr to filter on computed fields

C. The $match stage must come before $group to filter correctly

D. The $group stage syntax is incorrect

Solution

1. Step 1: Identify the invalid $match syntax

   The $match stage uses aggregation expression syntax { $gt: ["$total", 100] } directly, which is not valid query selector syntax.

2. Step 2: Use $expr for aggregation expressions

   To use expression operators like $gt with field paths and literals in array form, wrap in $expr: { $match: { $expr: { $gt: ["$total", 100] } } }.

3. Final Answer:

   The $match stage should use $expr to filter on computed fields -> Option B

4. Quick Check:

   $expr enables agg expressions in $match [OK]

Hint: Use $expr in $match after $group [OK]

Common Mistakes:

• Trying to filter grouped fields without $expr
• Placing $match before $group expecting same results
• Assuming $group syntax is wrong

5. You want to find the top 3 most expensive products with status 'A'. Which pipeline correctly applies the stages for best performance?

hard

A. db.products.aggregate([
{ $sort: { price: -1 } },
{ $limit: 3 },
{ $match: { status: 'A' } }
])

B. db.products.aggregate([
{ $limit: 3 },
{ $match: { status: 'A' } },
{ $sort: { price: -1 } }
])

C. db.products.aggregate([
{ $match: { status: 'A' } },
{ $sort: { price: -1 } },
{ $limit: 3 }
])

D. db.products.aggregate([
{ $match: { status: 'A' } },
{ $limit: 3 },
{ $sort: { price: -1 } }
])

Solution

1. Step 1: Filter early for performance

   Applying $match first reduces documents to only those with status 'A'.

2. Step 2: Sort and limit after filtering

   Sorting after filtering is faster, then $limit picks top 3.

3. Step 3: Check other options

   db.products.aggregate([ { $sort: { price: -1 } }, { $limit: 3 }, { $match: { status: 'A' } } ]) sorts all documents before filtering, wasting resources. db.products.aggregate([ { $limit: 3 }, { $match: { status: 'A' } }, { $sort: { price: -1 } } ]) limits before filtering, wrong results. db.products.aggregate([ { $match: { status: 'A' } }, { $limit: 3 }, { $sort: { price: -1 } } ]) limits before sorting, wrong order.

4. Final Answer:

   db.products.aggregate([ { $match: { status: 'A' } }, { $sort: { price: -1 } }, { $limit: 3 } ]) -> Option C

5. Quick Check:

   Filter, then sort, then limit [OK]

Hint: Filter first, then sort, then limit [OK]

Common Mistakes:

• Sorting before filtering wastes resources
• Limiting before sorting gives wrong top results
• Filtering after limiting misses correct documents