Schema validation in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is schema validation in Express?

Schema validation in Express is a way to check if the data sent by a user matches the expected format before processing it. It helps keep the app safe and working correctly.

beginner

Which library is commonly used for schema validation in Express apps?

Joi is a popular library used to define and check schemas in Express apps. It makes writing validation rules easy and clear.

intermediate

How do you apply schema validation in an Express route?

You create a schema with rules, then check the request data against it inside the route. If data is invalid, you send an error response; otherwise, continue processing.

beginner

What happens if the data does not match the schema during validation?

If data does not match the schema, the validation fails and you usually send back an error message explaining what is wrong, preventing bad data from entering your app.

beginner

Why is schema validation important in web applications?

Schema validation helps protect your app from wrong or harmful data, improves user experience by giving clear feedback, and keeps your app stable and secure.

What is the main purpose of schema validation in Express?

A To check if user data matches expected format

B To speed up the server response

C To style the webpage

D To store data in a database

Schema validation ensures the data sent by users fits the expected format before processing.

Which library is commonly used for schema validation in Express?

A React

B Lodash

C Joi

D Express-validator

Joi is a popular library for defining and validating schemas in Express apps.

What should you do if validation fails in an Express route?

A Send an error response explaining the problem

B Ignore the error and continue

C Restart the server

D Log the user out

When validation fails, send an error response to inform the user about the invalid data.

Schema validation helps to:

A Make the app look prettier

B Prevent bad data from entering the app

C Increase database size

D Speed up internet connection

Validation prevents incorrect or harmful data from entering the app.

Where do you usually perform schema validation in an Express app?

A In the browser console

B In the CSS file

C In the database

D In the route handler before processing data

Validation is done in the route handler to check incoming data before using it.

Explain how schema validation works in an Express route and why it is useful.

Think about the steps from receiving data to deciding if it is okay to use.

Describe the benefits of using a library like Joi for schema validation in Express.

Consider how Joi helps both developers and users.

Practice

1. What is the main purpose of schema validation in an Express app?

easy

A. To store data permanently in the database

B. To speed up the server response time

C. To style the user interface automatically

D. To check if incoming data matches expected rules before processing

Solution

1. Step 1: Understand schema validation role

   Schema validation ensures data received matches rules like type and format.

2. Step 2: Identify main purpose in Express

   It prevents bad data from causing errors or security issues by checking before use.

3. Final Answer:

   To check if incoming data matches expected rules before processing -> Option D

4. Quick Check:

   Schema validation = data check before use [OK]

Hint: Schema validation means checking data fits rules before use [OK]

Common Mistakes:

• Thinking validation speeds up server
• Confusing validation with UI styling
• Assuming validation stores data

2. Which of the following is the correct way to define a Joi schema for a required string named username?

easy

A. const schema = Joi.object({ username: Joi.string().required() });

B. const schema = Joi.string().required();

C. const schema = Joi.string().optional();

D. const schema = Joi.number().required();

Solution

1. Step 1: Recall Joi schema structure for objects

   Joi schemas for objects use Joi.object({ key: rule }) format.

2. Step 2: Check correct rule for required string property

   Property username must be a string and required, so use Joi.string().required().

3. Final Answer:

   const schema = Joi.object({ username: Joi.string().required() }); -> Option A

4. Quick Check:

   Object schema with required string property = const schema = Joi.object({ username: Joi.string().required() }); [OK]

Hint: Use Joi.object({ key: Joi.type().required() }) for required fields [OK]

Common Mistakes:

• Defining schema as Joi.string() alone for object data
• Using optional() instead of required()
• Using wrong data type like Joi.number() for string

3. Given this Joi schema and data, what will schema.validate(data) return?

const schema = Joi.object({ age: Joi.number().min(18).required() });
const data = { age: 16 };

medium

A. Validation fails because age is less than 18

B. Validation passes with value { age: 16 }

C. Validation fails because age is missing

D. Validation passes with value { age: 18 }

Solution

1. Step 1: Analyze schema rules for age

   Age must be a number, minimum 18, and required.

2. Step 2: Check data against schema

   Data has age 16, which is less than minimum 18, so validation fails.

3. Final Answer:

   Validation fails because age is less than 18 -> Option A

4. Quick Check:

   Age < 18 fails min rule = Validation fails because age is less than 18 [OK]

Hint: Check min/max rules carefully when validating numbers [OK]

Common Mistakes:

• Assuming 16 passes min(18) rule
• Confusing missing field with invalid value
• Thinking Joi changes value automatically

4. What is wrong with this Express route using Joi validation?

app.post('/user', (req, res) => {
  const schema = Joi.object({ email: Joi.string().email().required() });
  const result = schema.validate(req.body.email);
  if (result.error) {
    res.status(400).send('Invalid email');
  } else {
    res.send('User created');
  }
});

medium

A. It does not call next() after validation

B. It validates only the email string, not the whole object

C. It uses res.send instead of res.json

D. It should use Joi.number() for email

Solution

1. Step 1: Check what is validated

   The schema expects an object with an email property, but code validates req.body.email (a string).

2. Step 2: Understand Joi object validation

   To validate the whole object, pass req.body to schema.validate, not just one property.

3. Final Answer:

   It validates only the email string, not the whole object -> Option B

4. Quick Check:

   Validate whole object, not single property [OK]

Hint: Validate req.body object, not a single field string [OK]

Common Mistakes:

• Validating only a property instead of full object
• Confusing res.send and res.json (both work)
• Forgetting to call next() is not required here
• Using wrong Joi type for email

5. You want to validate a user object with optional phone that must be a string of 10 digits if present, and a required name string. Which Joi schema correctly enforces this?

hard

A. Joi.object({ name: Joi.string().required(), phone: Joi.string().pattern(/\d+/).required() })

B. Joi.object({ name: Joi.string(), phone: Joi.number().length(10).optional() })

C. Joi.object({ name: Joi.string().required(), phone: Joi.string().pattern(/^\d{10}$/).optional() })

D. Joi.object({ name: Joi.string().required(), phone: Joi.string().length(10).required() })

Solution

1. Step 1: Identify required and optional fields

   Name is required string; phone is optional string matching exactly 10 digits.

2. Step 2: Check regex pattern and optional usage

   Pattern /^\d{10}$/ matches exactly 10 digits; phone is optional, so use .optional().

3. Step 3: Eliminate incorrect options

   Other options make phone required, use wrong types like Joi.number(), apply invalid methods like .length(10) on numbers, or use loose patterns like /\d+/.

4. Final Answer:

   Joi.object({ name: Joi.string().required(), phone: Joi.string().pattern(/^\d{10}$/).optional() }) -> Option C

5. Quick Check:

   Required name + optional 10-digit phone pattern = Joi.object({ name: Joi.string().required(), phone: Joi.string().pattern(/^\d{10}$/).optional() }) [OK]

Hint: Use .pattern(/^\d{10}$/) for exact 10-digit string [OK]

Common Mistakes:

• Using Joi.number() for phone instead of string
• Making optional field required
• Using .length(10) on string without pattern
• Using loose regex that allows wrong formats