Why process management matters in Node.js - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is process management important in Node.js?

Which of the following best explains why process management is crucial in Node.js applications?

A It allows Node.js to run only one process at a time to prevent memory leaks.

B It helps handle multiple requests efficiently by managing child processes and avoiding blocking the event loop.

C It automatically converts JavaScript code into machine code for faster execution.

D It replaces the need for asynchronous programming by using synchronous calls.

💡 Hint

Think about how Node.js handles many users at once without slowing down.

Node.js uses an event loop that runs in a single thread. Process management, like creating child processes, helps handle heavy tasks without blocking this loop, keeping the app responsive.

❓ component_behavior

intermediate

What happens when a child process exits unexpectedly?

Consider a Node.js app that spawns a child process to handle a task. What is the expected behavior when the child process exits unexpectedly?

A The main process can listen for the 'exit' event and restart the child process if needed.

B The main process ignores the child process exit and continues without any notification.

C The child process automatically restarts without any code needed in the main process.

D The main process crashes immediately without any error handling.

💡 Hint

Think about how you can keep your app running smoothly even if a part of it stops.

Node.js allows the main process to listen for child process events like 'exit'. This way, it can handle unexpected exits by restarting the child process or logging the error.

📝 Syntax

advanced

Identify the correct way to spawn a child process in Node.js

Which code snippet correctly spawns a child process to run a script named worker.js using Node.js child_process module?

Node.js

const { spawn } = require('child_process');

// Choose the correct option below

A const child = spawn(['node', 'worker.js']);

B const child = spawn('worker.js');

C const child = spawn('node worker.js');

D const child = spawn('node', ['worker.js']);

💡 Hint

Remember that spawn takes the command as first argument and an array of arguments as second.

The spawn function requires the command as a string and the arguments as an array. Option D correctly uses 'node' as the command and ['worker.js'] as the argument array.

🔧 Debug

advanced

Why does this child process code not restart on exit?

Review the code below. Why does the child process not restart after it exits?

Node.js

const { spawn } = require('child_process');

function startChild() {
  const child = spawn('node', ['worker.js']);
  child.on('exit', () => {
    console.log('Child exited');
  });
}

startChild();

A Because the child process is not listening for the 'exit' event itself.

B Because the <code>spawn</code> function is used incorrectly and does not create a child process.

C Because the 'exit' event handler does not call <code>startChild()</code> again to restart the child process.

D Because the main process is blocking and cannot restart the child process.

💡 Hint

Look at what happens inside the 'exit' event handler.

The code logs when the child exits but does not restart it. To restart, the 'exit' event handler must call startChild() again.

❓ state_output

expert

What is the output of this process management code?

Consider the following Node.js code that manages a child process. What will be printed to the console?

Node.js

const { spawn } = require('child_process');

let restartCount = 0;

function startChild() {
  const child = spawn('node', ['-e', "console.log('Child running'); process.exit(1);"]);

  child.on('exit', (code) => {
    console.log(`Child exited with code ${code}`);
    if (restartCount < 2) {
      restartCount++;
      startChild();
    } else {
      console.log('Max restarts reached');
    }
  });
}

startChild();

A

Child running
Child exited with code 1
Child running
Child exited with code 1
Child running
Child exited with code 1
Max restarts reached

B

Child exited with code 1
Child exited with code 1
Child exited with code 1
Max restarts reached

C

Child running
Child running
Child running
Max restarts reached

D

Child running
Child exited with code 0
Max restarts reached

💡 Hint

Count how many times the child process starts and exits before stopping.

The child process prints 'Child running' then exits with code 1. The main process restarts it twice (total 3 runs). After the third exit, it prints 'Max restarts reached'.