Why middleware is fundamental in Node.js - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary role of middleware in Node.js web frameworks?

Middleware functions are used in Node.js web frameworks like Express. What is their main purpose?

A To compile JavaScript code into machine code for faster execution

B To directly send HTML pages to the client without any processing

C To handle requests and responses by processing data before reaching the final route handler

D To replace the need for a database in the application

💡 Hint

Think about how middleware acts between the client request and the final response.

Middleware functions sit between the incoming request and the final route handler. They can modify the request or response, perform checks, or add data before the final response is sent.

❓ component_behavior

intermediate

How does middleware affect the flow of request handling?

Consider this Express middleware chain:

app.use((req, res, next) => { console.log('First'); next(); });
app.use((req, res, next) => { console.log('Second'); next(); });
app.get('/', (req, res) => { res.send('Done'); });

What will be printed in the console when a GET request is made to '/'?

A Second\nFirst

B First\nSecond

C Done

D No output because next() is missing

💡 Hint

Middleware functions run in the order they are added and call next() to continue.

The first middleware logs 'First' and calls next(), then the second logs 'Second' and calls next(), finally the route handler sends 'Done'. The console shows 'First' then 'Second'.

📝 Syntax

advanced

Identify the error in this middleware function

Look at this middleware code snippet:

app.use((req, res, next) => {
  if (!req.user) {
    res.status(401).send('Unauthorized');
  }
  next();
});

What problem will this cause when a request has no user?

A It will send 'Unauthorized' but then call next(), causing headers to be sent twice error

B It will throw a syntax error because next() is missing parentheses

C It will not send any response and hang forever

D It will correctly block unauthorized requests without errors

💡 Hint

Think about what happens after sending a response in middleware.

After sending a response, calling next() continues to the next middleware or route, which tries to send another response, causing an error.

❓ state_output

advanced

What is the final response body after this middleware chain?

Given this Express setup:

app.use((req, res, next) => {
  req.customData = 'Hello';
  next();
});
app.use((req, res, next) => {
  req.customData += ' World';
  next();
});
app.get('/', (req, res) => {
  res.send(req.customData);
});

What will the client receive when requesting '/'?

A An error because req.customData is undefined

B "Hello"

C "World"

D "Hello World"

💡 Hint

Middleware can add or change properties on the request object.

The first middleware sets req.customData to 'Hello'. The second adds ' World'. The route sends the combined string.

🔧 Debug

expert

Why does this middleware never end the request?

Examine this middleware:

app.use((req, res, next) => {
  if (req.path === '/stop') {
    return res.send('Stopped');
  } else {
    next();
  }
});

Requests to '/stop' hang and never complete. Why?

A Because the middleware is missing a return statement after res.send() to stop execution

B Because the middleware does not call next() for '/stop' paths, so Express waits forever

C Because res.send() is asynchronous and needs await keyword

D Because res.send() is called but next() is not stopped, causing the request to hang

💡 Hint

Think about what happens after res.send() inside an if block.

Without a return after res.send(), the function continues and may cause unexpected behavior. Adding return stops further execution.