Why routing matters in Express - Challenge Your Understanding

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a route matches in Express?

Consider this Express code snippet:

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

What will the server send back when a client requests /hello?

Express

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

A The server sends back an empty response

B The server responds with a 404 Not Found error

C The server responds with the text 'Hello World!'

D The server crashes with an error

💡 Hint

Think about what the res.send method does in Express.

When the route matches '/hello', the callback runs and sends 'Hello World!' as the response body.

📝 Syntax

intermediate

Identify the syntax error in this route definition

Look at this Express route:

app.get('/user/:id' (req, res) => { res.send(req.params.id); });

What is wrong with this code?

Express

app.get('/user/:id' (req, res) => { res.send(req.params.id); });

A Missing comma between path and callback function

B Using arrow function instead of regular function

C Incorrect use of req.params.id

D Missing semicolon after res.send

💡 Hint

Check the parameters passed to app.get carefully.

The route path and the callback function must be separated by a comma.

❓ state_output

advanced

What is the output when multiple routes match?

Given this Express code:

app.get('/item/:id', (req, res) => { res.send('Item ' + req.params.id); });
app.get('/item/special', (req, res) => { res.send('Special Item'); });

What will the server respond to a request for /item/special?

Express

app.get('/item/:id', (req, res) => { res.send('Item ' + req.params.id); });
app.get('/item/special', (req, res) => { res.send('Special Item'); });

A 'Special Item'

B 'Item special'

C 404 Not Found

D Server error

💡 Hint

Express matches routes in the order they are defined.

The first route matches '/item/:id' and captures 'special' as id, so it responds with 'Item special'. The second route is never reached.

🔧 Debug

advanced

What happens when a route handler calls next()?

Look at this Express code:

app.get('/api/data', (req, res, next) => { next(); });
app.get('/api/data', (req, res) => { res.send('Data loaded'); });

When a client requests /api/data, what happens?

Express

app.get('/api/data', (req, res, next) => { next(); });
app.get('/api/data', (req, res) => { res.send('Data loaded'); });

A The server crashes with an error

B The server hangs and never responds

C The server responds with 404 Not Found

D The server responds with 'Data loaded'

💡 Hint

Think about what calling next() does in a route handler.

Calling next() in the first handler passes control to the next matching route handler (the second one), which sends 'Data loaded'. Express chains multiple handlers for the same path and method.

🧠 Conceptual

expert

Why is route order important in Express?

Imagine you have these routes:

app.get('/user/:id', handler1);
app.get('/user/profile', handler2);

What is the effect of defining /user/:id before /user/profile?

A Requests to '/user/profile' will be handled by handler1, not handler2

B Requests to '/user/profile' will be handled by handler2 as expected

C Requests to '/user/profile' will cause the server to crash

D Express will throw an error about duplicate routes

💡 Hint

Express matches routes in the order they are defined and stops at the first match.

Since '/user/:id' matches any path starting with '/user/', including '/user/profile', it will catch that request first if defined before '/user/profile'. So handler2 never runs.