Why advanced patterns matter in Express - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a basic Express server that listens on port 3000.

Express

const express = require('express');
const app = express();
app.get('/', (req, res) => {
  res.send('Hello World!');
});
app.listen([1], () => {
  console.log('Server running');
});

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

A80

B8080

C5000

D3000

Attempts:

3 left

💡 Hint

Common Mistakes

Using a port number that is already in use by another service.

Leaving the port number blank or undefined.

The standard port for local Express servers is often 3000. This code starts the server on port 3000.

2fill in blank

medium

Complete the code to add middleware that parses JSON bodies in Express.

Express

const express = require('express');
const app = express();
app.use([1]());
app.post('/data', (req, res) => {
  res.json(req.body);
});

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

Aexpress.json

BbodyParser.json

CjsonParser

Dexpress.body

Attempts:

3 left

💡 Hint

Common Mistakes

Using bodyParser.json without importing body-parser.

Using incorrect middleware names.

Express has built-in middleware called express.json() to parse JSON request bodies.

3fill in blank

hard

Fix the error in the route handler to correctly send a JSON response.

Express

app.get('/user', (req, res) => {
  res.[1]({ name: 'Alice' });
});

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

Ajson

Brender

CsendFile

DsendText

Attempts:

3 left

💡 Hint

Common Mistakes

Using res.sendFile for JSON data.

Using res.render without a template engine.

To send a JSON response, use res.json() in Express.

4fill in blank

hard

Fill both blanks to create a route that handles URL parameters and sends them back.

Express

app.get('/user/:[1]', (req, res) => {
  const [2] = req.params.id;
  res.send(`User ID is ${id}`);
});

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

Aid

BuserId

Dparam

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatching parameter names and variable names.

Using undefined variables in the response.

The URL parameter is named 'id', so req.params.id accesses it. The variable to hold it should be 'id' to match the template string.

5fill in blank

hard

Fill all three blanks to create a middleware that logs request method and URL, then passes control.

Express

function logger(req, res, [1]) {
  console.log(`${req.method} ${req.[2]`);
  [3]();
}
app.use(logger);

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

Anext

Burl

DrequestUrl

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to call next() causing the request to hang.

Using incorrect parameter names.

The third parameter in middleware is 'next' to pass control. The URL is accessed via req.url. Calling next() continues to the next middleware.

Practice

1. Why is using advanced patterns like routers and middleware important in Express apps?

easy

A. They automatically fix bugs in the code.

B. They make the app run faster by skipping routes.

C. They help organize code and make it easier to maintain.

D. They reduce the size of the app's files.

Solution

1. Step 1: Understand the role of advanced patterns

   Advanced patterns like routers and middleware help separate concerns and organize code logically.

2. Step 2: Connect organization to maintenance

   Organized code is easier to read, update, and debug, which improves maintenance.

3. Final Answer:

   They help organize code and make it easier to maintain. -> Option C

4. Quick Check:

   Code organization = easier maintenance [OK]

Hint: Think: organized code is easier to manage [OK]

Common Mistakes:

• Assuming patterns speed up app performance directly
• Believing patterns fix bugs automatically
• Confusing file size with code organization

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

easy

A. const router = express.Router(); app.use('/path', router);

B. const router = new Router(); app.add('/path', router);

C. const router = express.Router; app.use(router, '/path');

D. const router = Router(); app.use('/path', router);

Solution

1. Step 1: Recall Express router syntax

   Express routers are created with express.Router() and attached with app.use(path, router).

2. Step 2: Check each option for correct syntax

   const router = express.Router(); app.use('/path', router); matches the correct syntax; others have wrong constructors or method names.

3. Final Answer:

   const router = express.Router(); app.use('/path', router); -> Option A

4. Quick Check:

   Router creation and use = const router = express.Router(); app.use('/path', router); [OK]

Hint: Remember: express.Router() then app.use(path, router) [OK]

Common Mistakes:

• Using 'new Router()' instead of 'express.Router()'
• Swapping arguments in app.use()
• Forgetting parentheses after Router

3. What will be the output when this Express middleware is used?

app.use((req, res, next) => {
  console.log('Middleware 1');
  next();
});
app.use((req, res) => {
  res.send('Hello');
  console.log('Middleware 2');
});

When a request is made, what appears in the console and what is sent to the client?

medium

A. Console: Middleware 1 then Middleware 2; Client: 'Hello'

B. Console: Middleware 2 then Middleware 1; Client: 'Hello'

C. Console: Middleware 1 only; Client: 'Hello'

D. Console: nothing; Client: no response

Solution

1. Step 1: Understand middleware flow

   The first middleware logs 'Middleware 1' and calls next(), so the second middleware runs.

2. Step 2: Analyze second middleware behavior

   The second middleware sends 'Hello' to client and logs 'Middleware 2'. Both console logs appear in order.

3. Final Answer:

   Console: Middleware 1 then Middleware 2; Client: 'Hello' -> Option A

4. Quick Check:

   Middleware order = logs then response [OK]

Hint: Middleware logs before sending response [OK]

Common Mistakes:

• Thinking console logs after res.send() won't run
• Assuming middleware order is reversed
• Believing next() is optional to continue

4. Identify the error in this Express route setup:

app.get('/user', (req, res) => {
  res.send('User page');
});
app.get('/user', (req, res) => {
  res.send('Another user page');
});

medium

A. res.send() cannot be used twice in the same app.

B. Missing next() call causes the second route to fail.

C. Routes must use app.post() instead of app.get().

D. Duplicate route paths cause only the first handler to run.

Solution

1. Step 1: Check route definitions

   Both routes use the same path '/user' with app.get(), which causes the first matching route to handle requests.

2. Step 2: Understand Express routing behavior

   Express matches routes in order and stops at the first match unless next() is called, so the second route is ignored.

3. Final Answer:

   Duplicate route paths cause only the first handler to run. -> Option D

4. Quick Check:

   Duplicate routes = first match wins [OK]

Hint: Same path routes: only first runs unless next() used [OK]

Common Mistakes:

• Thinking both routes run automatically
• Believing next() is required in route handlers
• Confusing HTTP methods with route conflicts

5. You want to create an Express app that uses a router for '/api' routes and a middleware to log request times only for those routes. Which pattern correctly applies this?

hard

A. Create router, add logging middleware globally with app.use(), then use router;

B. Create a router, add logging middleware to it, then use app.use('/api', router);

C. Add logging middleware globally with app.use(), then create router for '/api';

D. Use app.get('/api', loggingMiddleware, router);

Solution

1. Step 1: Understand middleware scope

   To log only '/api' routes, middleware must be attached to the router handling those routes.

2. Step 2: Apply middleware to router and mount router

   Create router, add logging middleware to it, then mount router on '/api' with app.use('/api', router).

3. Final Answer:

   Create a router, add logging middleware to it, then use app.use('/api', router); -> Option B

4. Quick Check:

   Router middleware limits logging to '/api' [OK]

Hint: Attach middleware to router, then mount router [OK]

Common Mistakes:

• Adding middleware globally when only '/api' needs it
• Trying to pass router as middleware in app.get()
• Not mounting router properly on '/api'