📖 Scenario: You work at a library that stores detailed book information in a MongoDB collection. Each book document contains many fields, including a large reviews array with hundreds of entries. To improve performance when showing book summaries, you want to fetch only a subset of fields, excluding the large reviews array.
🎯 Goal: Build a MongoDB query that retrieves only the title, author, and year fields from the books collection, excluding the reviews field to reduce data size.
📋 What You'll Learn
Create a books collection with three book documents including title, author, year, and reviews fields
Define a projection object to exclude the reviews field
Write a MongoDB query using find() with the projection to get only the subset of fields
Complete the query to return the cursor for further processing
💡 Why This Matters
🌍 Real World
Large documents with many fields or arrays can slow down queries and increase network load. Using the subset pattern by excluding large fields helps improve performance when only summary data is needed.
💼 Career
Database developers and administrators often optimize queries by projecting only necessary fields, especially when working with large documents in MongoDB or similar NoSQL databases.
Progress0 / 4 steps
1
Create the books collection with sample documents
Create a variable called books and assign it an array with these three objects exactly: { title: 'The Great Gatsby', author: 'F. Scott Fitzgerald', year: 1925, reviews: ['Excellent', 'Classic', 'Must read'] }, { title: '1984', author: 'George Orwell', year: 1949, reviews: ['Thought-provoking', 'Dystopian', 'Timeless'] }, { title: 'To Kill a Mockingbird', author: 'Harper Lee', year: 1960, reviews: ['Powerful', 'Emotional', 'Important'] }
MongoDB
Hint
Use a list of dictionaries with exact keys and values as shown.
2
Define a projection to exclude the reviews field
Create a variable called projection and set it to an object that excludes the reviews field by setting reviews: 0
MongoDB
Hint
Use { 'reviews': 0 } to exclude the reviews field in MongoDB projection.
3
Write the MongoDB find() query with the projection
Create a variable called query and assign it the result of calling db.books.find({}, projection) to fetch all documents but only the subset of fields
MongoDB
Hint
Use db.books.find({}, projection) to get all documents with the projection applied.
4
Complete the query to return the cursor for further use
Add a line to assign result to the cursor returned by query so it can be used later for iteration
MongoDB
Hint
Assign the cursor returned by find() to a variable called result.
Practice
(1/5)
1. What is the main purpose of using the subset pattern in MongoDB when working with large documents?
easy
A. To retrieve only specific fields from documents to reduce data size
B. To delete large documents from the collection
C. To create indexes on large documents
D. To merge multiple documents into one
Solution
Step 1: Understand subset pattern purpose
The subset pattern is used to get only the needed parts of large documents instead of the whole document.
Step 2: Identify the benefit
This reduces the amount of data sent over the network and improves performance.
Final Answer:
To retrieve only specific fields from documents to reduce data size -> Option A
Quick Check:
Subset pattern = retrieve specific fields [OK]
Hint: Subset pattern means get only needed fields [OK]
Common Mistakes:
Thinking it deletes documents
Confusing with indexing
Assuming it merges documents
2. Which of the following is the correct syntax to retrieve only the name and age fields from documents in a MongoDB collection named users?
easy
A. db.users.find({name: 1, age: 1})
B. db.users.find({}, {name: 1, age: 1})
C. db.users.find({name: 1, age: 1}, {})
D. db.users.find({}, {name: 0, age: 0})
Solution
Step 1: Understand find() parameters
The first parameter is the query filter (empty {} means all documents), the second is the projection specifying fields to include.
Step 2: Identify correct projection syntax
Using {name: 1, age: 1} includes only these fields in the result.
Final Answer:
db.users.find({}, {name: 1, age: 1}) -> Option B
Quick Check:
Projection with 1 includes fields [OK]
Hint: Use find({}, {field: 1}) to include fields [OK]
Common Mistakes:
Putting projection in the first argument
Using 0 instead of 1 to include fields
Omitting the empty filter {}
3. Given the collection products with documents containing _id, name, price, and details fields, what will be the output of this query?
db.products.find({}, {name: 1, price: 1, _id: 0})
medium
A. Documents with only name and price fields, excluding _id
B. Documents with all fields including _id
C. Documents with only _id field
D. Syntax error due to excluding _id
Solution
Step 1: Analyze projection fields
The projection includes name and price with 1, and excludes _id with 0.
Step 2: Understand MongoDB default behavior
By default, _id is included unless explicitly excluded. Here it is excluded.
Final Answer:
Documents with only name and price fields, excluding _id -> Option A
Quick Check:
Projection includes name, price; excludes _id [OK]
Hint: Use _id:0 to exclude _id field [OK]
Common Mistakes:
Assuming _id is always included
Thinking projection excludes all other fields automatically
Confusing 0 and 1 in projection
4. You wrote this query to get only the title and author fields from books collection:
db.books.find({}, {title: 1, author: 0})
Why does this query cause an error or unexpected result?
medium
A. MongoDB requires _id to be included explicitly
B. Missing filter condition in find()
C. Projection keys must be strings, not identifiers
D. Mixing inclusion and exclusion in projection causes error
Solution
Step 1: Check projection rules
MongoDB does not allow mixing inclusion (1) and exclusion (0) in the same projection except for _id.
Step 2: Identify the problem in given projection
Here, title is included (1) and author is excluded (0), which is invalid.
Final Answer:
Mixing inclusion and exclusion in projection causes error -> Option D
Quick Check:
Projection must be all include or all exclude except _id [OK]
Hint: Use only 1s or only 0s in projection except _id [OK]
Common Mistakes:
Mixing 1 and 0 in projection fields
Forgetting _id can be excluded separately
Assuming filter is mandatory for projection
5. You have a large collection orders with documents containing many fields including customer, items, total, and shipping. You want to fetch only customer and the total fields but exclude _id. Which query correctly applies the subset pattern for best performance?
hard
A. db.orders.find({}, {customer: 0, total: 0, _id: 0})
B. db.orders.find({}, {customer: 1, total: 1, _id: 1})
C. db.orders.find({}, {customer: 1, total: 1, _id: 0})
D. db.orders.find({}, {customer: 1, total: 0, _id: 0})
Solution
Step 1: Include needed fields
To get only customer and total, set them to 1 in projection.
Step 2: Exclude _id field
Set _id to 0 to exclude it from results.
Step 3: Avoid mixing inclusion and exclusion
All fields except _id must be included (1), no mixing with 0.
Final Answer:
db.orders.find({}, {customer: 1, total: 1, _id: 0}) -> Option C
Quick Check:
Include fields with 1, exclude _id with 0 [OK]
Hint: Include needed fields with 1, exclude _id with 0 [OK]
Common Mistakes:
Including _id by default
Mixing 1 and 0 in fields other than _id
Excluding needed fields accidentally
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.