Node.js Communication & Stakeholder Relations 2

Question 1

A product manager asks why the Node.js API occasionally returns 503 errors under load. Which approach best communicates the root cause?

Accepted Answer

Explain that the event loop is blocked by synchronous CPU-intensive tasks exceeding capacity

Answer

Blocking the event loop with CPU-intensive synchronous code prevents Node.js from handling new requests, causing 503s under load.

Question 2

A stakeholder requests real-time order status updates in your Node.js application. Which technology should you recommend and why?

Accepted Answer

WebSockets via the 'ws' library for persistent bidirectional communication

Answer

WebSockets provide persistent bidirectional connections ideal for real-time updates without the overhead of repeated HTTP requests.

Question 3

Your team uses EventEmitter for internal service communication. A developer emits an event with no registered listener. What happens by default?

Accepted Answer

The emission is silently ignored except for 'error' events which throw

Answer

Unhandled events are silently discarded, but an unhandled 'error' event causes Node.js to throw an uncaught exception.

Question 4

A client complains that your API gives no useful error messages. Which Node.js practice best improves error communication?

Accepted Answer

Return appropriate HTTP status codes with structured JSON error bodies including a message and error code

Answer

Returning proper HTTP status codes with structured error bodies gives clients actionable information without exposing sensitive internals.

Question 5

You need to notify stakeholders whenever a background Node.js job completes. Which pattern is most appropriate?

Accepted Answer

Emit a custom event via EventEmitter or publish to a message queue like Redis Pub/Sub

Answer

EventEmitter or a message queue decouples job completion notification from the job itself, enabling reliable stakeholder notification.

Node.js Practice Test