Node.js Professional Standards & Competencies 2

Question 1

Which Node.js best practice helps prevent callback hell in production codebases?

Accepted Answer

Adopting Promises or async/await to flatten async flows

Answer

Promises and async/await flatten deeply nested callbacks, improving readability and maintainability.

Question 2

What is the professional standard for handling uncaught exceptions in a Node.js production service?

Accepted Answer

Log the error and allow the process to crash, relying on a process manager to restart it

Answer

The recommended pattern is to log the error, perform cleanup if needed, and let the process exit so a process manager (PM2, systemd) can restart it cleanly.

Question 3

Which tool is the professional standard for enforcing consistent code style across a Node.js team?

Accepted Answer

ESLint with a shared config and Prettier for formatting

Answer

ESLint catches code quality issues and Prettier enforces formatting, together standardizing style across teams.

Question 4

What does semantic versioning (semver) require when you make a backward-incompatible API change in a Node.js package?

Accepted Answer

Increment the major version (e.g., 2.0.0)

Answer

Breaking changes require a major version bump so consumers know to expect incompatibilities.

Question 5

A developer stores API keys directly in source code committed to a public GitHub repository. What professional standard was violated?

Accepted Answer

The practice of keeping secrets out of source control

Answer

Secrets must be stored in environment variables or secret managers, never committed to version control.

Node.js Practice Test

Node.js Practice Test

Node.js Professional Standards & Competencies 2