Node.js Communication & Stakeholder Relations 3

Question 1

Your Node.js service uses Server-Sent Events (SSE). How does SSE differ from WebSockets in stakeholder-facing communication scenarios?

Accepted Answer

SSE is server-to-client only and simpler; WebSockets support full bidirectional messaging

Answer

SSE is a unidirectional server-push mechanism over HTTP, while WebSockets provide full-duplex communication over a separate protocol.

Question 2

A DevOps stakeholder asks how to monitor your Node.js service health. Which built-in or common approach do you recommend?

Accepted Answer

Expose a /health endpoint that reports status, uptime, and memory usage

Answer

A /health endpoint is the standard pattern for health checks, integrating with load balancers, Kubernetes probes, and monitoring tools.

Question 3

A team member proposes using process.send() for inter-process communication in a Node.js cluster. When is this appropriate?

Accepted Answer

When communicating between a cluster master and its worker processes

Answer

process.send() works specifically for IPC between a cluster master and forked workers, or between parent and child processes created with fork().

Question 4

A stakeholder asks why some Node.js API responses arrive out of order. You suspect Promise.all() behavior. What do you explain?

Accepted Answer

Promise.all() runs promises concurrently; results are in input order but completion times vary

Answer

Promise.all() executes concurrently and returns results in the original input order, but individual operations complete at different times.

Question 5

You are writing a Node.js library for external developers. Which approach best communicates breaking changes?

Accepted Answer

Follow semantic versioning — bump the major version and document changes in a CHANGELOG

Answer

Semantic versioning signals breaking changes via major version bumps, and a CHANGELOG documents what changed and migration steps.

Node.js Practice Test