Creating documents in Express - Practice Exercises

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Express route handler?

Consider this Express route that creates a new document in a MongoDB collection using Mongoose. What will the client receive when this route is called successfully?

Express

app.post('/items', async (req, res) => {
  const item = new Item({ name: req.body.name });
  await item.save();
  res.status(201).json({ id: item._id, name: item.name });
});

A {"id":"<some_id>","name":"<name_from_request>"} with HTTP status 201

B A plain text message 'Item created' with HTTP status 201

C A JSON with the entire item document including __v and timestamps

D An empty response with HTTP status 200

💡 Hint

Look at what is sent in the response and the status code.

The route creates a new item, saves it, then responds with status 201 and a JSON containing only the id and name fields.

📝 Syntax

intermediate

Which option correctly creates a new document and handles errors in Express?

Identify the correct Express route code that creates a new document and sends a 500 status if saving fails.

A

app.post('/users', (req, res) => {
  const user = new User(req.body);
  user.save();
  res.status(201).json(user);
});

B

app.post('/users', async (req, res) => {
  try {
    const user = new User(req.body);
    await user.save();
    res.status(201).json(user);
  } catch (e) {
    res.status(500).send('Error');
  }
});

C

app.post('/users', async (req, res) => {
  const user = new User(req.body);
  await user.save();
  res.json(user);
});

D

app.post('/users', async (req, res) => {
  try {
    const user = new User(req.body);
    user.save();
    res.status(201).json(user);
  } catch (e) {
    res.status(500).send('Error');
  }
});

💡 Hint

Look for proper async/await usage and error handling.

Option B uses async/await correctly and catches errors to send a 500 status. Option B does not wait for save to complete. Option B lacks error handling. Option B misses await on save, so errors won't be caught.

🔧 Debug

advanced

Why does this Express route not save the document?

This route is supposed to create and save a new document but the database remains unchanged. What is the cause?

Express

app.post('/posts', (req, res) => {
  const post = new Post(req.body);
  post.save();
  res.status(201).json({ message: 'Post created' });
});

A The HTTP method should be GET to create documents.

B The Post model is not imported, causing a ReferenceError.

C The route is missing res.end(), so the response never finishes.

D post.save() is asynchronous but not awaited, so errors are not caught and save may not complete before response.

💡 Hint

Think about asynchronous operations and their completion.

post.save() returns a promise. Without awaiting it or handling the promise, the save may not finish before sending the response, causing the document not to be saved.

❓ state_output

advanced

What is the value of 'result' after this Express route runs?

Given this code snippet, what will be the value of the variable 'result' after the route is called?

Express

let result = null;
app.post('/data', async (req, res) => {
  const doc = new Data(req.body);
  result = await doc.save();
  res.status(201).json(result);
});

A An object representing the saved document including _id and other fields

B null, because 'result' is not updated outside the async function

C undefined, since 'result' is declared but never assigned

D A promise object representing the save operation

💡 Hint

Consider how async/await updates variables in the same scope.

'result' is assigned the resolved value of doc.save(), which is the saved document object including its _id.

🧠 Conceptual

expert

Which option best describes the role of middleware when creating documents in Express?

When building an Express app that creates documents, what is the primary purpose of middleware functions in the request handling chain?

A To send the final response to the client after document creation

B To directly save documents to the database without route handlers

C To process and validate incoming data before the document is created

D To replace the need for database models and schemas

💡 Hint

Think about what middleware does before the main route logic.

Middleware functions run before route handlers and are used to process, validate, or transform request data before creating documents.