Why Express for Node.js web servers - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is Express popular for Node.js web servers?

Which of the following best explains why Express is widely used for building web servers in Node.js?

A Express provides a minimal and flexible framework that simplifies routing and middleware management.

B Express automatically compiles Node.js code into faster machine code for better performance.

C Express replaces Node.js core modules with its own proprietary modules for security.

D Express is a graphical user interface tool for designing web server layouts visually.

💡 Hint

Think about what Express adds on top of Node.js to make web server coding easier.

Express is popular because it offers a simple way to handle routing and middleware, making Node.js web servers easier to build and maintain.

❓ component_behavior

intermediate

What happens when you add middleware in Express?

Consider this Express code snippet adding middleware. What is the behavior when a request matches the middleware?

app.use((req, res, next) => {
  console.log('Middleware called');
  next();
});

A The middleware causes a syntax error because next() is missing parentheses.

B The message logs and the request ends immediately without reaching any route handlers.

C The message 'Middleware called' logs, then the request continues to the next middleware or route handler.

D The middleware blocks all requests and returns a 404 error automatically.

💡 Hint

What does calling next() inside middleware do?

Calling next() passes control to the next middleware or route handler, so the request continues processing after logging.

📝 Syntax

advanced

Identify the correct Express route syntax

Which option shows the correct syntax to define a GET route for path '/hello' that sends 'Hi!' as response?

A app.get('/hello', (req, res) => { res.send('Hi!'); });

B app.route('/hello').get = (req, res) => { res.send('Hi!'); };

C app.get('/hello', (request, response) => response.write('Hi!'));

D app.get('/hello', (req, res) => { res.write('Hi!'); res.end(); });

💡 Hint

Remember the Express method to send a response body in one call.

Option A uses app.get with a callback that calls res.send, which is the correct and simplest way to send a response.

❓ state_output

advanced

What is the output when multiple middleware modify res.locals?

Given this Express code, what will be the final response sent?

app.use((req, res, next) => {
  res.locals.value = 1;
  next();
});
app.use((req, res, next) => {
  res.locals.value += 2;
  next();
});
app.get('/', (req, res) => {
  res.send(`Value is ${res.locals.value}`);
});

A Value is undefined

B Value is 1

C Value is 2

D Value is 3

💡 Hint

Think about how res.locals is shared across middleware in the same request.

res.locals is an object shared during the request. The first middleware sets value to 1, the second adds 2, so final value is 3.

🔧 Debug

expert

Why does this Express app crash on startup?

Examine this Express app code. Why does it crash with a TypeError?

const express = require('express');
const app = express();

app.use(express.json());

app.get('/test', (req, res) => {
  res.send('Test route');
});

app.listen(3000, () => {
  console.log('Server started on port 3000');
});

A The app crashes because express.json() is not a valid middleware function.

B Middleware app.use(express.json()) is added after app.listen, so it never runs for requests.

C The app crashes because app.listen must be called before defining routes.

D The app crashes because res.send() is called without ending the response.

💡 Hint

Consider the order of middleware and server start.

Middleware must be added before starting the server to handle requests properly. Adding express.json() after app.listen means it won't run on incoming requests, causing unexpected behavior.