Resource naming conventions in Node.js - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Choosing RESTful resource names

Which of the following resource names follows the best RESTful naming convention for a collection of user profiles?

A /users

B /getUsers

C /userProfiles

D /user_profile

💡 Hint

Think about plural nouns and simplicity in RESTful URLs.

RESTful resource names should be plural nouns and simple. '/users' is the best choice because it clearly represents a collection of user resources.

❓ component_behavior

intermediate

Effect of inconsistent resource naming

What is the likely effect of using inconsistent resource naming like mixing singular and plural forms in API endpoints?

A It causes runtime errors in Node.js applications

B It automatically triggers validation errors

C It improves API flexibility and clarity

D It confuses API users and makes maintenance harder

💡 Hint

Consider the impact on developers using and maintaining the API.

Inconsistent naming does not cause runtime errors but makes the API confusing and harder to maintain.

📝 Syntax

advanced

Correct resource naming in Express route

Which Express route correctly follows resource naming conventions for accessing a single product by ID?

const express = require('express');
const router = express.Router();

router.get( /* your code here */, (req, res) => {
  res.send('Product details');
});

A '/product/:id'

B '/products/:id'

C '/getProduct/:id'

D '/products/id'

💡 Hint

Remember to use plural nouns and colon for parameters.

Using '/products/:id' follows RESTful conventions: plural resource name and parameter for ID.

🔧 Debug

advanced

Identify naming issue causing confusion

Given these two Express routes, which naming issue can cause confusion or bugs?

router.get('/user', (req, res) => { res.send('All users'); });
router.get('/users/:id', (req, res) => { res.send('User details'); });

A Using singular '/user' for all users is inconsistent with plural '/users/:id'

B Routes are fine; no naming issues

C Both routes use plural resource names correctly

D Missing colon in '/users/:id' causes parameter parsing error

💡 Hint

Check singular vs plural usage in resource names.

Using singular '/user' for a collection is inconsistent with plural '/users/:id' for a single resource, which can confuse API users.

❓ lifecycle

expert

Impact of resource naming on API versioning and lifecycle

How can poor resource naming conventions affect the lifecycle and versioning of a Node.js REST API?

A It automatically enables backward compatibility

B It has no effect on API lifecycle or versioning

C It forces breaking changes and complicates version upgrades

D It simplifies adding new features without version changes

💡 Hint

Think about how naming affects API stability and client expectations.

Poor naming can lead to breaking changes when fixing inconsistencies, making version upgrades harder and risking client breakage.