Skip to content

Nodejs Runtime Practice Exam

Test yourself under real exam conditions: 50 timed questions, 60 on the clock, pass mark 70%%. Instant score with a full review of everything you got wrong. Free — no account needed.

📝 50 questions · ⏱ 60 minutes · 🎯 Pass mark 70% · 🆓 Free, no signup

Exam details

  • 50 questions drawn from 50 cards
  • Countdown timer — auto-submits when time runs out
  • Pass mark 70% (real certification threshold)
  • Full review of wrong answers at the end
  • No signup required — save your score with a free account

Sample Questions

5 shown

What is Node.js?

Show ▼

Node.js is a JavaScript runtime built on Chrome's V8 engine. It allows running JavaScript outside the browser, using an event-driven, non-blocking I/O model that makes it lightweight and efficient for building scalable network applications.

What is the Node.js event loop?

Show ▼

The event loop is the mechanism that allows Node.js to perform non-blocking I/O operations despite JavaScript being single-threaded. It continuously checks the call stack and callback queue, executing callbacks when the stack is empty. Phases include: timers → pending callbacks → idle/prepare → poll → check → close callbacks.

What are the phases of the Node.js event loop?

Show ▼

  • Timers – executes setTimeout and setInterval callbacks
  • Pending callbacks – I/O callbacks deferred to next iteration
  • Poll – retrieves new I/O events
  • Check – executes setImmediate callbacks
  • Close callbacks – e.g. socket.on('close')

What is the difference between setImmediate() and setTimeout()?

Show ▼

setImmediate() executes in the check phase of the event loop, after the poll phase completes. setTimeout(fn, 0) executes in the timers phase on the next iteration. When called within an I/O callback, setImmediate() always fires before setTimeout().

What is process.nextTick() and how does it differ from setImmediate()?

Show ▼

process.nextTick() fires immediately after the current operation, before the event loop continues. It is processed on the microtask queue, not part of any event loop phase. setImmediate() fires on the next iteration of the event loop. Overusing nextTick can starve I/O.

🎯 Take the Nodejs Runtime Practice Exam