Why change streams are needed in MongoDB - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to watch for changes in the 'orders' collection.

MongoDB

const changeStream = db.collection('orders').[1]();

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

Aupdate

Bfind

Cinsert

Dwatch

Attempts:

3 left

💡 Hint

Common Mistakes

Using find() instead of watch() will only query existing data, not listen for changes.

Using insert() or update() are operations to modify data, not to watch changes.

The watch() method opens a change stream to listen for changes in a collection.

2fill in blank

medium

Complete the code to handle change events from the change stream.

MongoDB

changeStream.on('[1]', next => { console.log(next); });

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

Achange

Bclose

Cerror

Dopen

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'error' listens for errors, not data changes.

Using 'close' or 'open' are lifecycle events, not change notifications.

The change event fires when a change occurs in the watched collection.

3fill in blank

hard

Fix the error in the code to properly start watching changes on the 'users' collection.

MongoDB

const stream = db.collection('users').[1]();

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

Alisten

Bwatch

Con

Dsubscribe

Attempts:

3 left

💡 Hint

Common Mistakes

Passing 'change' as argument to watch() causes an error.

Using listen() or subscribe() are not valid MongoDB methods.

The watch() method does not take an event name as argument; it returns a change stream. The event name is used with on().

4fill in blank

hard

Fill both blanks to filter change events for only 'insert' operations.

MongoDB

const pipeline = [ { $match: { 'operationType': [1] } } ];
const stream = db.collection('products').[2](pipeline);

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

A'insert'

B'update'

Cwatch

Dfind

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'update' instead of 'insert' filters the wrong operation.

Using find() instead of watch() does not create a change stream.

The pipeline filters for 'insert' operations, and watch() starts the change stream with that filter.

5fill in blank

hard

Fill all three blanks to create a change stream that listens for deletes and logs the document key.

MongoDB

const pipeline = [ { $match: { 'operationType': [1] } } ];
const stream = db.collection('logs').[2](pipeline);
stream.on('[3]', change => { console.log(change.documentKey); });

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

A'delete'

Bwatch

Cchange

D'insert'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'insert' instead of 'delete' filters the wrong operation.

Using other event names than 'change' will not capture change events.

Using methods other than watch() will not create a change stream.

This code watches for 'delete' operations, starts the change stream with watch(), and listens for 'change' events to log the document key.

Practice

1. Why are MongoDB change streams needed in applications?

easy

A. To react instantly to database changes without polling

B. To backup the database automatically

C. To increase the size of the database

D. To encrypt data at rest

Solution

1. Step 1: Understand the purpose of change streams

   Change streams allow applications to listen for real-time changes in the database without repeatedly asking (polling) the database.

2. Step 2: Compare options with the purpose

   Options describing backup, size increase, and encryption are unrelated features, which are not the purpose of change streams.

3. Final Answer:

   To react instantly to database changes without polling -> Option A

4. Quick Check:

   Change streams = instant reaction to changes [OK]

Hint: Change streams = real-time updates without polling [OK]

Common Mistakes:

• Confusing change streams with backup features
• Thinking change streams increase database size
• Assuming change streams handle encryption

2. Which is the correct syntax to start watching changes on a MongoDB collection named orders?

easy

A. db.orders.track()

B. db.orders.listen()

C. db.orders.observe()

D. db.orders.watch()

Solution

1. Step 1: Recall the MongoDB method for change streams

   The official method to watch changes is watch() on a collection.

2. Step 2: Verify the options

   Only db.orders.watch() uses watch(), while others use incorrect or non-existent methods.

3. Final Answer:

   db.orders.watch() -> Option D

4. Quick Check:

   Use watch() to start change streams [OK]

Hint: Use watch() method to start change streams [OK]

Common Mistakes:

• Using listen() instead of watch()
• Trying observe() which is not a MongoDB method
• Using track() which does not exist

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

const changeStream = db.users.watch();
changeStream.on('change', (change) => {
  console.log(change.operationType);
});
// Then a new user document is inserted

medium

A. "delete"

B. "update"

C. "insert"

D. "replace"

Solution

1. Step 1: Understand the event listened to

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

2. Step 2: Identify the operation type for insertion

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

3. Final Answer:

   "insert" -> Option C

4. Quick Check:

   Insert operation logs "insert" [OK]

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

Common Mistakes:

• Confusing insert with update or delete operationType
• Expecting the whole document instead of operationType
• Thinking operationType is 'replace' for insert

4. You wrote this code to watch changes but it throws an error:

const changeStream = db.orders.watch({ $match: { operationType: 'insert' } });

What is the likely cause of the error?

medium

A. operationType cannot be filtered in change streams

B. The $match stage must be inside an array as a pipeline

C. watch() does not accept any arguments

D. db.orders is not a valid collection reference

Solution

1. Step 1: Check the argument format for watch()

   The watch() method accepts an array of pipeline stages, not a single object.

2. Step 2: Identify the correct way to filter

   The $match stage must be inside an array: [{ $match: { operationType: 'insert' } }].

3. Final Answer:

   The $match stage must be inside an array as a pipeline -> Option B

4. Quick Check:

   Pipeline stages must be in an array [OK]

Hint: Pass pipeline as array to watch() [OK]

Common Mistakes:

• Passing pipeline as object instead of array
• Thinking watch() takes no arguments
• Believing operationType filtering is not allowed

5. You want to build a live notification system that alerts users immediately when their order status changes. Why is using MongoDB change streams the best approach?

hard

A. They provide real-time updates without polling, reducing latency and load

B. They automatically send emails to users on changes

C. They backup order data every time it changes

D. They encrypt order status changes for security

Solution

1. Step 1: Identify the requirement for live notifications

   Live notifications need instant updates when data changes without delay.

2. Step 2: Match change streams benefits to the requirement

   Change streams provide real-time data change events without polling, which reduces latency and server load.

3. Step 3: Eliminate unrelated options

   Options describing automatic email sending, data backups, and encryption are unrelated to change streams' core function.

4. Final Answer:

   They provide real-time updates without polling, reducing latency and load -> Option A

5. Quick Check:

   Change streams = real-time, low-latency updates [OK]

Hint: Change streams enable instant updates, no polling needed [OK]

Common Mistakes:

• Assuming change streams send emails automatically
• Confusing change streams with backup or encryption
• Thinking polling is required for live updates