C100DEV Aggregation Framework Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  To filter the pipeline based on multiple conditions.

  Why it's wrong here

  $merge is an output stage, not a filtering stage. $match is the operator used for filtering documents. Using $merge will attempt to write the current aggregation result set into a target collection, which is unrelated to the process of filtering data streams within the pipeline itself.

• ✗

  To replace the entire contents of a collection with new results.

  Why it's wrong here

  Replacing a collection is the specific function of the $out stage. $merge, by contrast, allows for more granular control over how the results are integrated into the target collection, enabling developers to update existing documents or insert new ones based on defined match criteria rather than total replacement.

• ✓

  To write results into a collection, optionally updating existing documents.

  Why this is correct

  $merge allows for complex output scenarios, including updating existing documents (upserting) and inserting new documents. This makes it a powerful tool for incremental data processing and maintaining synchronized aggregate collections without needing to drop and recreate the entire target collection during every pipeline execution cycle.

• ✗

  To sort the final output before it is returned to the client.

  Why it's wrong here

  $sort is used for ordering documents. $merge is strictly an output stage designed for persisting aggregation results back to the database. It does not provide any sorting functionality, and attempting to use it for that purpose would result in a syntax error or a failure to achieve the goal.