Why streams are needed in Node.js - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use streams for large files in Node.js?

You want to read a very large file in Node.js. Why is using streams better than reading the whole file at once?

A Streams convert the file into a database for easier access.

B Streams automatically compress the file to make it smaller in memory.

C Streams load the entire file into memory but faster than other methods.

D Streams let you process the file piece by piece, so you use less memory and start working faster.

💡 Hint

Think about memory use when handling big files.

Streams allow reading or writing data in small chunks. This means you don't need to load the entire file into memory, which saves resources and improves performance.

❓ component_behavior

intermediate

What happens when you pipe a readable stream to a writable stream?

In Node.js, you connect a readable stream to a writable stream using pipe(). What is the main effect of this connection?

Node.js

const fs = require('fs');
const readable = fs.createReadStream('input.txt');
const writable = fs.createWriteStream('output.txt');
readable.pipe(writable);

A The entire file is copied instantly before any processing.

B The writable stream sends data back to the readable stream.

C Data flows automatically from the readable stream to the writable stream in chunks.

D The streams merge into one stream that reads and writes at the same time.

💡 Hint

Consider how data moves between streams.

Using pipe() connects streams so data flows in chunks from the source (readable) to the destination (writable) automatically.

❓ state_output

advanced

What is the output when reading a file with streams?

Consider this Node.js code reading a file with a stream. What will be printed to the console?

Node.js

const fs = require('fs');
const readable = fs.createReadStream('file.txt', { encoding: 'utf8' });
readable.on('data', chunk => {
  console.log(chunk.length);
});

A Multiple numbers showing the length of each chunk read from the file.

B One number showing the total length of the file.

C An error because chunk.length is undefined.

D No output because the stream does not emit 'data' events.

💡 Hint

Streams emit 'data' events multiple times for chunks.

The 'data' event fires for each chunk read. Each chunk has a length, so multiple numbers print showing chunk sizes.

📝 Syntax

advanced

Identify the syntax error in this stream code

Which option contains a syntax error when creating a readable stream in Node.js?

Node.js

const fs = require('fs');
const stream = fs.createReadStream('data.txt', { encoding: 'utf8' });

A const stream = fs.createReadStream('data.txt' encoding: 'utf8');

B const stream = fs.createReadStream('data.txt', { encoding: 'utf8' });

C const stream = fs.createReadStream('data.txt', encoding = 'utf8');

D const stream = fs.createReadStream('data.txt', { encoding: utf8 });

💡 Hint

Check the commas and braces in the options.

Option A is missing a comma between arguments, causing a syntax error.

🔧 Debug

expert

Why does this stream code cause a memory leak?

This Node.js code reads a large file but causes increasing memory use until crash. What is the likely cause?

Node.js

const fs = require('fs');
const readable = fs.createReadStream('largefile.txt');
readable.on('data', chunk => {
  // process chunk but do not consume it fully
});

A The file is too large to read with streams, so memory leaks always happen.

B The 'data' event handler does not pause the stream, causing data to accumulate in memory.

C The stream is missing an 'end' event listener, causing memory leaks.

D The encoding option is missing, so chunks are not released from memory.

💡 Hint

Think about how streams manage flow control.

If the 'data' event handler does not consume or pause the stream, data buffers grow, causing memory leaks.