Use cases for change streams in MongoDB - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Primary use case of MongoDB change streams

Which of the following is the main purpose of using change streams in MongoDB?

A To track real-time changes in the database and react immediately

B To perform batch updates on large collections

C To create backups of the database automatically

D To optimize query performance by indexing

💡 Hint

Think about how applications can respond instantly to data changes.

Change streams allow applications to listen for real-time changes in MongoDB collections and databases, enabling immediate reactions to inserts, updates, deletes, and more.

❓ query_result

intermediate

Output of a change stream watching insert operations

Given a change stream watching only insert operations on a collection, what will be the output when a new document is inserted?

MongoDB

db.collection.watch([{ $match: { operationType: 'insert' } }])

A A document describing the deleted document with operationType 'delete'

B An error because operationType 'insert' is invalid

C No output because change streams do not track inserts

D A document describing the inserted document with operationType 'insert'

💡 Hint

Consider what operationType 'insert' means in change streams.

When watching for inserts, the change stream outputs documents describing each inserted document with operationType set to 'insert'.

📝 Syntax

advanced

Correct syntax to watch changes on a database

Which of the following is the correct syntax to open a change stream on an entire MongoDB database?

A db.watch()

B db.getMongo().watch()

C db.getSiblingDB('mydb').watch()

D db.getMongo().getDB('mydb').watch()

💡 Hint

Think about how to access a database object and then call watch on it.

To watch changes on a database, you must get the database object and call watch() on it. The correct way is db.getSiblingDB('mydb').watch().

❓ optimization

advanced

Optimizing change stream filters

To reduce the amount of data your application processes, which approach optimizes change stream usage best?

A Use a $match stage in the change stream pipeline to filter only needed operation types

B Fetch all changes and filter them in the application code

C Use change streams without any filters to get all changes

D Disable change streams and poll the database every minute

💡 Hint

Filtering early reduces unnecessary data transfer and processing.

Using a $match stage in the change stream pipeline filters changes at the database level, reducing network and processing load.

🧠 Conceptual

expert

Use case best suited for MongoDB change streams

Which scenario is best suited for implementing MongoDB change streams?

A Running complex aggregation queries on large datasets periodically

B Building a real-time notification system that alerts users when their data changes

C Archiving old data to cold storage every month

D Creating indexes to speed up read queries

💡 Hint

Change streams are designed for real-time data change tracking.

Change streams enable applications to react instantly to data changes, making them ideal for real-time notifications.

Practice

1. What is a primary use case for MongoDB change streams?

easy

A. To get real-time notifications when data changes in the database

B. To backup the entire database automatically

C. To create indexes on collections

D. To run complex aggregation queries

Solution

1. Step 1: Understand what change streams do

   Change streams allow applications to listen for changes in MongoDB collections or databases in real time.

2. Step 2: Identify the main use case

   This feature is mainly used to get notified instantly when data changes, enabling live updates or triggers.

3. Final Answer:

   To get real-time notifications when data changes in the database -> Option A

4. Quick Check:

   Change streams = real-time notifications [OK]

Hint: Change streams = instant reaction to data changes [OK]

Common Mistakes:

• Confusing change streams with backup tools
• Thinking change streams create indexes
• Assuming change streams run queries

2. Which of the following is the correct syntax to start a change stream on a collection named orders in MongoDB?

easy

A. db.orders.streamChanges()

B. db.orders.changeStream()

C. db.orders.listen()

D. db.orders.watch()

Solution

1. Step 1: Recall the MongoDB change stream method

   The correct method to open a change stream on a collection is watch().

2. Step 2: Match the method to the collection

   Calling db.orders.watch() starts watching changes on the orders collection.

3. Final Answer:

   db.orders.watch() -> Option D

4. Quick Check:

   Change stream method = watch() [OK]

Hint: Change streams start with .watch() on collections [OK]

Common Mistakes:

• Using non-existent methods like changeStream()
• Confusing with listen() or streamChanges()
• Missing parentheses after watch

3. Given the following code snippet, what will be the output when a new document is inserted into the products collection?

const changeStream = db.products.watch();
changeStream.on('change', (change) => {
  console.log(change.operationType);
});

medium

A. Nothing will print because the listener is incorrect

B. "insert" will be printed to the console

C. An error will occur because watch requires parameters

D. "update" will be printed to the console

Solution

1. Step 1: Understand the change stream event listener

   The code listens for any change events on the products collection and logs the operationType.

2. Step 2: Identify the operation type for insert

   When a new document is inserted, the operationType is "insert".

3. Final Answer:

   "insert" will be printed to the console -> Option B

4. Quick Check:

   Insert triggers operationType = "insert" [OK]

Hint: Insert triggers operationType 'insert' in change stream [OK]

Common Mistakes:

• Thinking watch() needs parameters to work
• Confusing operationType values
• Assuming listener syntax is wrong

4. You wrote this code to watch changes on the users collection but it throws an error:

const changeStream = db.users.watch({ fullDocument: 'updateLookup' });
changeStream.on('change', (change) => {
  console.log(change.fullDocument);
});

What is the likely cause of the error?

medium

A. The fullDocument option should be passed as the second argument to watch() after the pipeline array

B. The fullDocument option value should be 'updateLookup' without quotes

C. The watch method does not accept any options

D. The watch method requires a callback function as the first argument

Solution

1. Step 1: Review correct usage of watch options

   The watch method accepts an optional aggregation pipeline array as the first argument, and options as the second argument.

2. Step 2: Identify the mistake in option placement

   Passing { fullDocument: 'updateLookup' } directly as the first argument is incorrect; it should be the second argument after the pipeline array.

3. Final Answer:

   The fullDocument option should be passed as the second argument to watch() after the pipeline array -> Option A

4. Quick Check:

   Options go as second argument to watch() [OK]

Hint: Options are second argument in watch(), not first [OK]

Common Mistakes:

• Passing options as first argument instead of second
• Removing quotes from string option values
• Expecting watch() to take a callback argument

5. You want to build a live dashboard that updates instantly when orders are inserted or updated in the orders collection. Which approach using change streams is best to minimize data transfer and improve performance?

hard

A. Poll the orders collection every 5 seconds instead of using change streams

B. Watch the entire orders collection without filters and send full documents on every change

C. Use a change stream with a pipeline to filter only insert and update operations and project only needed fields

D. Use change streams but ignore the update operations to reduce complexity

Solution

1. Step 1: Identify the goal for live dashboard updates

   The dashboard needs instant updates only for inserts and updates, not deletes or other operations.

2. Step 2: Choose efficient change stream usage

   Filtering the change stream with a pipeline to watch only insert and update operations and projecting only necessary fields reduces data sent and improves performance.

3. Final Answer:

   Use a change stream with a pipeline to filter only insert and update operations and project only needed fields -> Option C

4. Quick Check:

   Filter and project in change streams for efficiency [OK]

Hint: Filter and project in change streams to optimize data [OK]

Common Mistakes:

• Watching all changes without filters wastes bandwidth
• Polling is less efficient than change streams
• Ignoring updates misses important dashboard changes