Aggregation Pipelines have a limit of:

The correct answer is D. 16 MB document and 100 MB RAM. MongoDB Aggregation Pipelines are bound by two key limits: 16 MB per document (the standard BSON document size limit that applies throughout MongoDB) and 100 MB of RAM per pipeline stage before you must enable allowDiskUse. Option D captures both constraints correctly. Why the…

MongoDB Fundamentals

Question

Options

ANo limit on document and 100 MB RAM
C2 MB document and 100 MB RAM
D16 MB document and 100 MB RAM

How the community answered

(28 responses)

A
4% (1)
C
7% (2)
D
89% (25)

Explanation

MongoDB Aggregation Pipelines are bound by two key limits: 16 MB per document (the standard BSON document size limit that applies throughout MongoDB) and 100 MB of RAM per pipeline stage before you must enable allowDiskUse. Option D captures both constraints correctly.

Why the distractors are wrong:

Option A ("no limit on document") is incorrect - the 16 MB BSON document size cap always applies, including to pipeline output documents.
Option C ("2 MB document") confuses the aggregation document limit with the deprecated 16 MB result limit that older MongoDB versions imposed on find() responses - not the document size itself.

Memory tip: Think "16 and 100" - 16 MB is MongoDB's universal document ceiling (applies everywhere, not just aggregation), and 100 MB is the RAM budget per stage before you need disk spillover via allowDiskUse: true.

Topics

#aggregation pipeline#memory limits#document size limit#pipeline constraints

Community Discussion

No community discussion yet for this question.

Full C100DBA Practice