Why the event system matters in Node.js - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use an event-driven system in Node.js?

Node.js uses an event-driven system. What is the main benefit of this design?

A It allows Node.js to handle many tasks at the same time without waiting for each to finish.

B It makes Node.js run slower because it waits for events to happen.

C It forces Node.js to use multiple CPU cores automatically.

D It stops Node.js from running any code until all events are processed.

💡 Hint

Think about how Node.js can manage many users or tasks without delays.

Node.js uses events to handle many tasks without blocking. This means it can start a task, then move on to others while waiting for the first to finish, making it efficient.

❓ component_behavior

intermediate

What happens when an event is emitted?

In Node.js, when an event is emitted, what happens next?

Node.js

const EventEmitter = require('events');
const emitter = new EventEmitter();
emitter.on('greet', () => console.log('Hello!'));
emitter.emit('greet');

A The event is ignored because no callback is provided.

B Nothing happens because events need to be awaited.

C The program crashes because 'greet' is not a built-in event.

D The 'greet' event triggers the listener and prints 'Hello!' to the console.

💡 Hint

Look at what the listener does when the event is emitted.

When 'greet' is emitted, the listener runs and prints 'Hello!'. Events trigger their listeners immediately.

🔧 Debug

advanced

Why does this event listener not run?

Look at this code. Why does the listener not print anything?

Node.js

const EventEmitter = require('events');
const emitter = new EventEmitter();
emitter.emit('start');
emitter.on('start', () => console.log('Started!'));

A The event is emitted before the listener is added, so the listener misses it.

B The listener function has a syntax error and does not run.

C The event name 'start' is invalid and ignored.

D Node.js does not support multiple listeners for the same event.

💡 Hint

Think about the order of adding listeners and emitting events.

Listeners must be added before the event is emitted. Here, the event fires before the listener exists, so nothing happens.

❓ state_output

advanced

What is the output of this event count code?

What will this code print?

Node.js

const EventEmitter = require('events');
const emitter = new EventEmitter();
let count = 0;
emitter.on('ping', () => count++);
emitter.emit('ping');
emitter.emit('ping');
console.log(count);

A undefined

B 1

C 2

D 0

💡 Hint

Count how many times the 'ping' event is emitted and the listener runs.

The listener runs twice, increasing count each time, so the final count is 2.

📝 Syntax

expert

Which option correctly creates a custom event emitter class?

Choose the correct way to create a class that emits a 'ready' event when started.

A class MyEmitter extends require('events') { start() { this.emit('ready'); } }

B const EventEmitter = require('events'); class MyEmitter extends EventEmitter { start() { this.emit('ready'); } }

C const EventEmitter = require('events'); function MyEmitter() { this.emit('ready'); }

D class MyEmitter { constructor() { this.emit('ready'); } }

💡 Hint

Remember how to extend EventEmitter properly in Node.js.

Option B correctly imports EventEmitter, extends it, and emits 'ready' inside a method.