Why modular routing matters in Express - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import Express and create a router.

Express

const express = require('express');
const router = express.[1]();

Drag options to blanks, or click blank then click option'

Aapp

Brouter

Croute

DRouter

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase 'router' instead of 'Router'

Using 'route' which is incorrect

Use express.Router() to create a modular router instance.

2fill in blank

medium

Complete the code to define a GET route on the router.

Express

router.[1]('/', (req, res) => {
  res.send('Hello from modular route!');
});

Drag options to blanks, or click blank then click option'

Apost

Bget

Cuse

Dlisten

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'post' instead of 'get'

Using 'use' which is for middleware

The get method defines a GET route handler.

3fill in blank

hard

Fix the error in exporting the router from the module.

Express

module.exports = [1];

Drag options to blanks, or click blank then click option'

Aexpress

Bapp

Crouter

DRouter

Attempts:

3 left

💡 Hint

Common Mistakes

Exporting 'express' or 'app' instead of 'router'

Export the router instance to use it in other files.

4fill in blank

hard

Fill both blanks to mount the modular router in the main app.

Express

const express = require('express');
const app = express();
const userRoutes = require('./routes/users');

app.[1]('/users', [2]);

Drag options to blanks, or click blank then click option'

Ause

Blisten

CuserRoutes

Dget

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'listen' instead of 'use'

Passing wrong variable instead of router

Use app.use to mount the router at the '/users' path.

5fill in blank

hard

Fill all three blanks to create a modular route that handles POST requests and exports correctly.

Express

const express = require('express');
const router = express.[1]();

router.[2]('/submit', (req, res) => {
  res.send('Form submitted');
});

module.exports = [3];

Drag options to blanks, or click blank then click option'

ARouter

Bpost

Crouter

Droute

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase 'router()' to create router

Using 'route' instead of 'post'

Exporting wrong variable

Create a router with Router(), define a POST route with post, and export the router.

Practice

1. Why is modular routing important in Express applications?

easy

A. It allows routes to run without defining HTTP methods.

B. It automatically improves server speed without code changes.

C. It helps organize routes into separate files for easier maintenance.

D. It removes the need to use express.Router().

Solution

1. Step 1: Understand modular routing purpose

   Modular routing splits routes into separate files to keep code organized and easier to maintain.

2. Step 2: Evaluate other options

   The other options describe incorrect or unrelated effects: allowing routes without HTTP methods, automatic speed improvement, and removing the need for express.Router().

3. Final Answer:

   It helps organize routes into separate files for easier maintenance. -> Option C

4. Quick Check:

   Modular routing = better organization [OK]

Hint: Modular routing means splitting routes into files [OK]

Common Mistakes:

• Thinking modular routing speeds up server automatically
• Believing modular routing removes need for express.Router()
• Assuming routes work without HTTP methods

2. Which of the following is the correct way to create a modular router in Express?

easy

A. const router = express.createRouter();

B. const router = express.Router();

C. const router = new Router();

D. const router = express.route();

Solution

1. Step 1: Recall Express router creation syntax

   The correct method to create a router is express.Router().

2. Step 2: Check other options

   The other options use methods that do not exist or are incorrect: express.createRouter(), new Router(), and express.route().

3. Final Answer:

   const router = express.Router(); -> Option B

4. Quick Check:

   Router creation = express.Router() [OK]

Hint: Use express.Router() to create a router [OK]

Common Mistakes:

• Using express.createRouter() which does not exist
• Trying to instantiate Router without express
• Calling express.route() instead of express.Router()

3. Given this Express app code, what will be the output when accessing /users?

const express = require('express');
const app = express();
const userRouter = express.Router();

userRouter.get('/', (req, res) => res.send('User list'));
app.use('/users', userRouter);

app.listen(3000);

medium

A. User list

B. Cannot GET /users

C. Error: userRouter is not defined

D. 404 Not Found

Solution

1. Step 1: Analyze route setup

   The userRouter handles GET requests at '/' and is mounted at '/users'. So, '/users' triggers the router's '/' route.

2. Step 2: Determine response

   The router sends 'User list' when '/users' is accessed.

3. Final Answer:

   User list -> Option A

4. Quick Check:

   Mounted router '/' + '/users' = '/users' response [OK]

Hint: Router path + mount path combine for final route [OK]

Common Mistakes:

• Expecting 'Cannot GET /users' due to missing route
• Confusing router path with app path
• Thinking mounting changes route handler path

4. What best describes this modular routing code?

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

router.get('/items', (req, res) => res.send('Items list'));
app.use(router);

app.listen(3000);

medium

A. Router is not mounted with a path, so '/items' will be reachable.

B. Router should be created with new express.Router().

C. The route should use app.get, not router.get.

D. app.listen should be called before defining routes.

Solution

1. Step 1: Analyze router mounting

   The router is mounted without a path via app.use(router), so its routes like GET /items are registered directly on the app and reachable at /items.

2. Step 2: Evaluate other options

   Router creation uses express.Router() as a factory function, not new; router.get is correct for modularity; app.listen can follow route definitions.

3. Final Answer:

   Router is not mounted with a path, so '/items' will be reachable. -> Option A

4. Quick Check:

   Router mounted without path handles routes as defined [OK]

Hint: Mount router with path or use routes as defined [OK]

Common Mistakes:

• Thinking express.Router() needs 'new' keyword
• Believing router must be mounted with a path
• Assuming app.listen order matters for routes

5. You have two route modules: adminRouter handling / and userRouter handling /. You mount them as:

app.use('/admin', adminRouter);
app.use('/admin', userRouter);

What problem can arise and how to fix it?

hard

A. Only the first router works; fix by combining routes into one router.

B. No problem; Express merges routes automatically without conflicts.

C. Server crashes; fix by renaming routers to different variable names.

D. Routes conflict; fix by mounting userRouter on a different path like '/users'.

Solution

1. Step 1: Understand route mounting conflict

   Mounting two routers on the same path '/admin' with overlapping routes causes conflicts and unexpected behavior.

2. Step 2: Identify fix

   Mounting userRouter on a different path like '/users' avoids conflicts and keeps routes clear.

3. Final Answer:

   Routes conflict; fix by mounting userRouter on a different path like '/users'. -> Option D

4. Quick Check:

   Same mount path + overlapping routes = conflict [OK]

Hint: Avoid mounting different routers on same path with same routes [OK]

Common Mistakes:

• Assuming Express merges conflicting routes automatically
• Thinking variable names affect route conflicts
• Believing combining routers is the only fix