Schema versioning strategies in MongoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a version field to a MongoDB document.

MongoDB

db.collection.insertOne({ name: "Alice", age: 30, version: [1] })

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

A1

B"v1"

Ctrue

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of a number for version.

Omitting the version field entirely.

The version field is typically a number to track schema versions. Here, 1 is used.

2fill in blank

medium

Complete the code to update the schema version of all documents to 2.

MongoDB

db.collection.updateMany({}, { $set: { version: [1] } })

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

A2

B"2"

Ctrue

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string "2" instead of number 2.

Using null or true instead of a version number.

Schema versions are numeric. Here, we set version to 2 as a number.

3fill in blank

hard

Fix the error in the query to find documents with version 1.

MongoDB

db.collection.find({ version: [1] })

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

A"1"

B1

Ctrue

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string "1" which does not match the numeric field.

Using true or null which are incorrect types.

The version field is stored as a number, so the query must use number 1, not string "1".

4fill in blank

hard

Fill both blanks to add a new field only to documents with version less than 2.

MongoDB

db.collection.updateMany({ version: { [1]: 2 } }, { $set: { [2]: "legacy" } })

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

A$lt

B$gt

Cstatus

Dversion

Attempts:

3 left

💡 Hint

Common Mistakes

Using $gt instead of $lt for filtering.

Setting the field name as 'version' which overwrites existing data.

Use $lt to find documents with version less than 2, and add a new field 'status' with value 'legacy'.

5fill in blank

hard

Fill all three blanks to rename the field 'oldField' to 'newField' in documents with version 1.

MongoDB

db.collection.updateMany({ version: [1] }, { $rename: { [2]: [3] } })

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

A1

B"oldField"

C"newField"

D"version"

Attempts:

3 left

💡 Hint

Common Mistakes

Using version as a string instead of number.

Not quoting field names in $rename operator.

We filter documents with version 1, then rename 'oldField' to 'newField' using $rename operator.

Practice

1. What is the main purpose of adding a schemaVersion field in MongoDB documents?

easy

A. To track changes in the document structure over time

B. To improve query performance automatically

C. To encrypt the document data

D. To store user authentication details

Solution

1. Step 1: Understand schemaVersion role

   The schemaVersion field is used to mark which version of the document structure is currently in use.

2. Step 2: Identify its purpose in schema versioning

   This helps developers know what format the data is in and apply necessary migrations when the schema changes.

3. Final Answer:

   To track changes in the document structure over time -> Option A

4. Quick Check:

   schemaVersion tracks structure changes = C [OK]

Hint: Remember schemaVersion marks document format version [OK]

Common Mistakes:

• Thinking schemaVersion improves query speed
• Confusing schemaVersion with encryption
• Assuming schemaVersion stores user info

2. Which of the following is the correct way to add a schemaVersion field with value 2 to a MongoDB document using an update query?

easy

A. db.collection.updateOne({ _id: id }, { $push: { schemaVersion: 2 } })

B. db.collection.updateOne({ _id: id }, { schemaVersion: 2 })

C. db.collection.updateOne({ _id: id }, { $set: { schemaVersion: 2 } })

D. db.collection.updateOne({ _id: id }, { $inc: { schemaVersion: 2 } })

Solution

1. Step 1: Recall MongoDB update syntax

   To set or update a field, use the $set operator with the new value.

2. Step 2: Check each option

   db.collection.updateOne({ _id: id }, { $set: { schemaVersion: 2 } }) correctly uses $set to assign schemaVersion: 2. Bare object updates lack an update operator (invalid), $push is for arrays, and $inc increments numbers.

3. Final Answer:

   db.collection.updateOne({ _id: id }, { $set: { schemaVersion: 2 } }) -> Option C

4. Quick Check:

   Use $set to update fields = A [OK]

Hint: Use $set to add or update fields in MongoDB [OK]

Common Mistakes:

• Forgetting to use $set operator
• Using $push for non-array fields
• Using $inc to set a fixed value

3. Given the following documents in a collection:

{ "_id": 1, "name": "Alice", "schemaVersion": 1 }

{ "_id": 2, "name": "Bob", "schemaVersion": 2 }

What will be the result of this query?

db.collection.find({ schemaVersion: { $lt: 2 } })

medium

A. [{ "_id": 1, "name": "Alice", "schemaVersion": 1 }, { "_id": 2, "name": "Bob", "schemaVersion": 2 }]

B. [{ "_id": 2, "name": "Bob", "schemaVersion": 2 }]

C. []

D. [{ "_id": 1, "name": "Alice", "schemaVersion": 1 }]

Solution

1. Step 1: Understand the query condition

   The query filters documents where schemaVersion is less than 2.

2. Step 2: Check each document against condition

   Document with schemaVersion 1 matches (1 < 2). Document with 2 does not (2 is not less than 2).

3. Final Answer:

   [{ "_id": 1, "name": "Alice", "schemaVersion": 1 }] -> Option D

4. Quick Check:

   schemaVersion < 2 returns only version 1 docs = D [OK]

Hint: Check numeric conditions carefully in queries [OK]

Common Mistakes:

• Including documents with schemaVersion equal to 2
• Returning empty result incorrectly
• Confusing $lt with $lte operator

4. You have a migration script to update documents from schemaVersion 1 to 2. The script uses:

db.collection.updateMany({ schemaVersion: 1 }, { $set: { schemaVersion: 2, newField: true } })

But after running, some documents still show schemaVersion 1. What is a likely cause?

medium

A. Documents were missing the schemaVersion field

B. The update query syntax is incorrect

C. The updateMany command does not support $set

D. The migration script ran on the wrong collection

Solution

1. Step 1: Analyze the update query filter

   The filter matches documents where schemaVersion equals 1 exactly.

2. Step 2: Consider documents missing the field

   If some documents lack the schemaVersion field, they won't match the filter and won't be updated.

3. Final Answer:

   Documents were missing the schemaVersion field -> Option A

4. Quick Check:

   Missing field means no match = B [OK]

Hint: Check if all docs have the field before filtering [OK]

Common Mistakes:

• Assuming updateMany syntax is wrong
• Believing $set is unsupported in updateMany
• Not verifying the collection name

5. You want to migrate documents from multiple schema versions to the latest version 3. Your current documents have schemaVersion 1 or 2. Which strategy best ensures all documents are updated correctly?

hard

A. Directly update all documents with version 1 or 2 to version 3 in one step

B. Run separate migration scripts: first update version 1 to 2, then update version 2 to 3

C. Delete all documents with version less than 3 and insert new ones

D. Ignore schemaVersion and update documents randomly

Solution

1. Step 1: Understand incremental migrations

   Updating schema versions step-by-step ensures each migration applies necessary changes safely.

2. Step 2: Evaluate options

   Run separate migration scripts: first update version 1 to 2, then update version 2 to 3 runs migrations in order: 1 to 2, then 2 to 3, preserving data integrity. Directly update all documents with version 1 or 2 to version 3 in one step risks skipping intermediate changes. Delete all documents with version less than 3 and insert new ones loses data. Ignore schemaVersion and update documents randomly is unsafe.

3. Final Answer:

   Run separate migration scripts: first update version 1 to 2, then update version 2 to 3 -> Option B

4. Quick Check:

   Incremental migrations keep data safe = A [OK]

Hint: Migrate stepwise through versions, not skipping steps [OK]

Common Mistakes:

• Trying to skip intermediate schema versions
• Deleting data instead of migrating
• Ignoring schemaVersion field