Node.js Professional Standards & Competencies 3

Question 1

What is the professional approach to structuring a large Node.js application to promote maintainability?

Accepted Answer

Organize code into feature-based or layer-based modules with clear separation of concerns

Answer

Modular architecture with clear separation of concerns makes large codebases easier to navigate, test, and maintain.

Question 2

When writing a Node.js library for public npm, what professional standard should guide your choice of dependencies?

Accepted Answer

Minimize dependencies to reduce the attack surface and installation size for consumers

Answer

Fewer dependencies mean less exposure to supply-chain attacks and a lighter footprint for library consumers.

Question 3

What does 'graceful shutdown' mean in the context of a professional Node.js service?

Accepted Answer

Stopping acceptance of new requests, finishing in-flight requests, then exiting cleanly

Answer

Graceful shutdown ensures no requests are dropped mid-processing when the service is restarted or scaled down.

Question 4

A Node.js API returns detailed stack traces to the client in production. What professional issue does this present?

Accepted Answer

It exposes internal implementation details and potential attack vectors to malicious users

Answer

Stack traces reveal file paths, library versions, and code structure that attackers can exploit.

Question 5

Which practice is a professional standard for Node.js API versioning?

Accepted Answer

Prefix routes with a version identifier (e.g., /api/v1/) and maintain older versions during transition periods

Answer

URL-based versioning clearly signals breaking changes to consumers and allows parallel support of multiple versions.

Node.js Practice Test