Joi as validation alternative in Express - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output when Joi validation fails?

Consider an Express route using Joi to validate a request body. If the validation fails, what will be the response sent to the client?

Express

const Joi = require('joi');
const schema = Joi.object({ name: Joi.string().min(3).required() });

app.post('/user', (req, res) => {
  const { error } = schema.validate(req.body);
  if (error) {
    return res.status(400).send(error.details[0].message);
  }
  res.send('User created');
});

A A 400 status with a message describing the first validation error

B A 200 status with 'User created' message regardless of input

C A 500 status with a server error message

D No response is sent, request hangs

💡 Hint

Think about what happens when Joi finds a problem in the input.

When Joi validation fails, the error object contains details about the failure. The code sends a 400 status with the first error message to inform the client about the invalid input.

📝 Syntax

intermediate

Which Joi schema correctly validates an email and age?

You want to validate a request body with two fields: email (required, valid email) and age (optional, integer, minimum 18). Which Joi schema is correct?

A Joi.object({ email: Joi.email().string().required(), age: Joi.integer().number().min(18) })

B Joi.object({ email: Joi.string().required(), age: Joi.number().integer().max(18) })

C Joi.object({ email: Joi.string().required().email(), age: Joi.number().min(18).integer() })

D Joi.object({ email: Joi.string().email().required(), age: Joi.number().integer().min(18) })

💡 Hint

Check the order and method names for Joi validation.

Option D uses the correct Joi methods in the right order: Joi.string().email().required() for email and Joi.number().integer().min(18) for age. Other options misuse method order or constraints.

🔧 Debug

advanced

Why does this Joi validation always pass?

This code is supposed to reject empty strings for the username, but it always passes validation. Why?

Express

const schema = Joi.object({ username: Joi.string().min(1) });
const result = schema.validate({ username: '' });
console.log(result.error);

A Because Joi.string() allows empty strings unless .required() or .empty() is used to forbid them

B Because .min(1) applies to numbers, not strings, so it does not enforce string length

C Because the validate method is asynchronous and result.error is always undefined

D Because Joi.string() allows empty strings by default; .min(1) checks length but empty string length is 0, so it should fail but it doesn't because .min(1) is ignored

💡 Hint

Think about how Joi treats empty strings by default.

Joi.string() allows empty strings unless you explicitly forbid them with .required() or .empty(). The .min(1) method checks length but empty strings are allowed unless forbidden.

❓ state_output

advanced

What is the value of validatedData after validation?

Given this code, what will be the value of validatedData after validation?

Express

const schema = Joi.object({ name: Joi.string().trim().required(), age: Joi.number().default(30) });
const input = { name: '  Alice  ' };
const { value: validatedData } = schema.validate(input);
console.log(validatedData);

A { name: 'Alice' }

B { name: ' Alice ', age: undefined }

C { name: 'Alice', age: 30 }

D { name: ' Alice ', age: 30 }

💡 Hint

Look at how Joi's trim and default work on the input.

The trim() method removes spaces around the string, so name becomes 'Alice'. The age field is missing in input, so Joi adds the default value 30.

🧠 Conceptual

expert

Why choose Joi over manual validation in Express?

Which of the following is the strongest reason to use Joi as a validation alternative in Express apps?

A Joi replaces the need for any error handling in Express routes

B Joi provides a declarative, reusable schema to validate and sanitize input, reducing bugs and improving maintainability

C Joi automatically fixes all invalid inputs without developer intervention

D Joi is faster than native JavaScript validation functions in all cases

💡 Hint

Think about what Joi offers beyond simple checks.

Joi lets you define clear, reusable validation rules that help catch errors early and keep code clean. It does not fix inputs automatically or remove the need for error handling. Performance depends on use case.