One-to-many referencing pattern in MongoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to find all orders for a customer with ID 123.

MongoDB

db.orders.find({ customer_id: [1] })

Drag options to blanks, or click blank then click option'

A123

B"123"

C"customer_id"

DObjectId("123")

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes around the number when the ID is stored as a number.

Using ObjectId when the ID is a simple number.

The customer_id field stores the customer's ID as a number, so we query with 123 without quotes.

2fill in blank

medium

Complete the code to insert a new order referencing customer ID 456.

MongoDB

db.orders.insertOne({ order_id: 1, customer_id: [1], items: 0 })

Drag options to blanks, or click blank then click option'

A456

B"customer_456"

CObjectId("456")

D"456"

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of a number for customer_id.

Using ObjectId when not appropriate.

The customer_id should match the type used in the database, which is a number here.

3fill in blank

hard

Fix the error in the query to find orders for customer ID 789.

MongoDB

db.orders.find({ customer_id: [1] })

Drag options to blanks, or click blank then click option'

A"789"

B789

CObjectId("789")

Dcustomer_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string or ObjectId instead of a number.

Using the field name as a value.

The customer_id is stored as a number, so the query must use the number 789 without quotes or ObjectId.

4fill in blank

hard

Fill both blanks to create a query that finds orders with more than 2 items for customer ID 101.

MongoDB

db.orders.find({ customer_id: [1], items: { $[2]: 2 } })

Drag options to blanks, or click blank then click option'

A101

Bgt

Cgte

Dlt

Attempts:

3 left

💡 Hint

Common Mistakes

Using $gte instead of $gt for strictly more than 2.

Using the wrong customer ID.

We query for customer_id 101 and use $gt to find orders with more than 2 items.

5fill in blank

hard

Fill all three blanks to update the customer name for customer ID 202.

MongoDB

db.customers.updateOne({ _id: [1] }, { $[2]: { name: [3] } })

Drag options to blanks, or click blank then click option'

A202

Bset

C"Alice"

D"202"

Attempts:

3 left

💡 Hint

Common Mistakes

Using string "202" instead of number 202 for _id.

Using wrong update operator like $update.

Not quoting the new name string.

The query matches the customer with _id 202 (number), uses $set to update, and sets the name to "Alice".

Practice

1. What is the main purpose of the one-to-many referencing pattern in MongoDB?

easy

A. To create a backup of documents automatically

B. To store all related data inside a single document

C. To link one document to many related documents using their IDs

D. To encrypt documents for security

Solution

1. Step 1: Understand one-to-many referencing

   It connects one document to many others by storing their IDs, not embedding all data.

2. Step 2: Compare options

   Only To link one document to many related documents using their IDs describes linking documents by IDs, which is the core of one-to-many referencing.

3. Final Answer:

   To link one document to many related documents using their IDs -> Option C

4. Quick Check:

   One-to-many referencing = linking documents by IDs [OK]

Hint: One-to-many means one document points to many IDs [OK]

Common Mistakes:

• Thinking all data is stored inside one document
• Confusing referencing with embedding
• Assuming it creates backups automatically

2. Which of the following is the correct way to reference many comments in a post document using one-to-many referencing in MongoDB?

easy

A. { _id: 1, title: 'Post', comments: [ObjectId('abc123'), ObjectId('def456')] }

B. { _id: 1, title: 'Post', comments: { text: 'Nice post!' } }

C. { _id: 1, title: 'Post', comments: 'This is a comment' }

D. { _id: 1, title: 'Post', comments: ObjectId('abc123') }

Solution

1. Step 1: Identify referencing format

   One-to-many referencing stores an array of ObjectIds pointing to related documents.

2. Step 2: Check each option

   { _id: 1, title: 'Post', comments: [ObjectId('abc123'), ObjectId('def456')] } uses an array of ObjectIds, which is correct. Others embed data or use a single ID incorrectly.

3. Final Answer:

   { _id: 1, title: 'Post', comments: [ObjectId('abc123'), ObjectId('def456')] } -> Option A

4. Quick Check:

   Array of ObjectIds = correct referencing [OK]

Hint: Use array of ObjectIds to reference many documents [OK]

Common Mistakes:

• Embedding comment text instead of IDs
• Using a single ObjectId for many comments
• Storing comments as plain strings

3. Given these two collections:
posts: [{ _id: 1, title: 'Hello', comments: [101, 102] }]
comments: [{ _id: 101, text: 'Nice!' }, { _id: 102, text: 'Great!' }]
What will be the result of this query to find comments for post with _id 1?
db.comments.find({ _id: { $in: db.posts.findOne({ _id: 1 }).comments } })

medium

A. [] (empty array)

B. [{ _id: 1, title: 'Hello', comments: [101, 102] }]

C. SyntaxError due to nested query

D. [{ _id: 101, text: 'Nice!' }, { _id: 102, text: 'Great!' }]

Solution

1. Step 1: Understand the query

   The inner findOne gets the comments array [101, 102] from post _id 1.

2. Step 2: Use $in to find matching comments

   The outer find returns comments with _id in [101, 102], so both comment documents are returned.

3. Final Answer:

   [{ _id: 101, text: 'Nice!' }, { _id: 102, text: 'Great!' }] -> Option D

4. Quick Check:

   Find comments by IDs in post = matching comment docs [OK]

Hint: Use $in with IDs array to get related documents [OK]

Common Mistakes:

• Expecting post document instead of comments
• Thinking nested query causes syntax error
• Getting empty result by mistake

4. You have this post document:
{ _id: 1, title: 'Test', comments: ['abc', 'def'] }
But when you run db.comments.find({ _id: { $in: post.comments } }), it returns no results. What is the most likely problem?

medium

A. ObjectIds in post.comments are strings, not ObjectId type

B. The comments collection has no documents with those ObjectIds

C. The query syntax is incorrect for $in operator

D. The post document is missing the comments field

Solution

1. Step 1: Check data types of referenced IDs

   If post.comments contains strings instead of ObjectId objects, the query won't match.

2. Step 2: Confirm query correctness

   The query syntax is correct, so the mismatch is likely due to type difference.

3. Final Answer:

   ObjectIds in post.comments are strings, not ObjectId type -> Option A

4. Quick Check:

   Type mismatch in IDs causes no matches [OK]

Hint: Ensure referenced IDs are ObjectId type, not strings [OK]

Common Mistakes:

• Assuming empty results mean syntax error
• Ignoring data type differences
• Thinking missing field causes this error

5. You want to design a blog system with users, posts, and comments. Each user can write many posts, and each post can have many comments. Using one-to-many referencing, which is the best way to organize references?

hard

A. comments store userId; posts store arrays of commentIds

B. posts store userId; comments store postId; users do not store references

C. users embed all posts; posts embed all comments

D. users store arrays of postIds; posts store arrays of commentIds

Solution

1. Step 1: Understand one-to-many referencing best practice

   Usually, the 'many' side stores the reference to the 'one' side to avoid large arrays.

2. Step 2: Apply to blog system

   Posts store userId (one user, many posts), comments store postId (one post, many comments), users don't store arrays.

3. Final Answer:

   posts store userId; comments store postId; users do not store references -> Option B

4. Quick Check:

   Many side stores reference to one side [OK]

Hint: Store reference on 'many' side to 'one' side document [OK]

Common Mistakes:

• Embedding all posts or comments inside users or posts
• Storing large arrays on 'one' side documents
• Confusing which side stores the reference