Node.js Communication & Stakeholder Relations 4

Question 1

A business analyst wants to understand your Node.js service's throughput. Which metric most clearly communicates capacity to non-engineers?

Accepted Answer

Requests per second (RPS) under normal and peak load

Answer

Requests per second is a universally understood throughput metric that directly maps to business capacity requirements.

Question 2

Your Node.js app uses child_process.fork() to offload CPU work. How do you communicate results back to the parent process?

Accepted Answer

Use process.send() in the child and listen for 'message' events on the ChildProcess object in the parent

Answer

Fork creates an IPC channel; child calls process.send(data) and the parent listens via childProcess.on('message', handler).

Question 3

A security stakeholder asks how your Node.js API prevents sensitive data from appearing in error logs. What is the best practice?

Accepted Answer

Sanitize error objects before logging by removing PII fields, passwords, and tokens

Answer

Sanitizing error objects before logging ensures passwords, tokens, and PII are stripped while preserving diagnostic information.

Question 4

You want to emit a deprecation warning to developers using an older version of your Node.js module. Which mechanism is preferred?

Accepted Answer

Use process.emitWarning() with type 'DeprecationWarning'

Answer

process.emitWarning() with type 'DeprecationWarning' integrates with Node.js's warning system and appears in logs without crashing the process.

Question 5

A stakeholder requests that your Node.js microservice notify an external webhook whenever an order ships. What pattern should you implement?

Accepted Answer

Use an HTTP POST from Node.js to the stakeholder's webhook URL upon order ship event

Answer

Webhooks push event data via HTTP POST to an external URL, enabling real-time integration without the receiver needing to poll.

Node.js Practice Test