C100DEV Flashcards — Free MongoDB Certified Associate Developer Study Cards

Embed variable attributes directly within each product document.

Using a polymorphic schema with optional fields directly in the document is the canonical MongoDB approach. This strategy avoids the JOIN operations required by relational databases when attributes are stored in separate tables. By keeping data together, developers achieve high performance for read operations and take full advantage of MongoDB's indexing capabilities on specific document fields, regardless of whether every document contains that field.

It automatically indexes all fields in every document.

Setting 'dynamic' to true enables Atlas Search to automatically index all fields in every document within the collection. This is useful for rapid prototyping or collections with unpredictable schemas. However, it can significantly increase the size of the index and consume more resources compared to manual mappings. Understanding this balance is critical for developers managing performance and cost when dealing with large datasets and varying document structures in search-enabled collections.

$match

The $match stage filters documents before they pass to subsequent stages, significantly reducing the data volume processed by memory-intensive operations like $sort or $group. Placing it first allows MongoDB to utilize indexes, which minimizes disk I/O and RAM usage. Efficient pipeline construction is critical for scalability in production environments, as reducing the input set early directly impacts the latency and resource consumption of the entire aggregation operation.

{ userId: 1, timestamp: -1 }

To avoid an in-memory sort, the index direction must match the query's sort direction for the sorted fields. Since `userId` is filtered via equality and `timestamp` is sorted descending, the index `{ userId: 1, timestamp: -1 }` allows MongoDB to traverse the index naturally in the required order, ensuring optimal query performance and preventing sorting memory limit errors during execution.

Setting the { upsert: true } option in updateOne or findOneAndUpdate.

The upsert option instructs MongoDB to insert a new document if no existing document matches the query filter. When combined with update operators, the final document is constructed by merging the query filter with the update operators, which is crucial for idempotent bootstrapping patterns.

Implementing the Attribute Pattern with an array of key-value pairs.

The Attribute Pattern is the standard solution for schemas with heterogeneous fields. By transforming fields into an array of key-value pairs (k: 'color', v: 'red'), you create a uniform structure that allows for single-index coverage across all attributes. This avoids the limitations of sparse indexes and allows the application to query arbitrary attributes without needing to modify the document structure or rebuild large index sets frequently.