Defining models in Express - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Mongoose library.

Express

const mongoose = require([1]);

Drag options to blanks, or click blank then click option'

A"fs"

B"express"

C"mongoose"

D"http"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'express' instead of 'mongoose'.

Forgetting the quotes around the package name.

We import Mongoose by requiring the "mongoose" package.

2fill in blank

medium

Complete the code to define a new Mongoose schema.

Express

const userSchema = new mongoose.[1]({ name: String, age: Number });

Drag options to blanks, or click blank then click option'

AModel

BSchema

CDocument

DCollection

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Model' instead of 'Schema'.

Confusing schema with collection.

We create a schema using mongoose.Schema.

3fill in blank

hard

Fix the error in the code to create a model from the schema.

Express

const User = mongoose.model('User', [1]);

Drag options to blanks, or click blank then click option'

AuserSchema

BuserSchema()

CUserSchema

DUser

Attempts:

3 left

💡 Hint

Common Mistakes

Calling userSchema as a function.

Using capitalized 'UserSchema' when the variable is lowercase.

The model function expects the schema object, which is userSchema.

4fill in blank

hard

Fill both blanks to define a schema with a required string field and a number field.

Express

const productSchema = new mongoose.[1]({ name: { type: String, [2]: true }, price: Number });

Drag options to blanks, or click blank then click option'

ASchema

Brequired

Cunique

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'unique' instead of 'required' for mandatory fields.

Using 'Model' instead of 'Schema' for schema definition.

We use Schema to define the schema and required: true to make the field mandatory.

5fill in blank

hard

Fill all three blanks to create and export a Mongoose model named 'Order' with a schema having a date and total fields.

Express

const orderSchema = new mongoose.[1]({ date: Date, total: Number });
const Order = mongoose.[2]('Order', [3]);
module.exports = Order;

Drag options to blanks, or click blank then click option'

ASchema

Bmodel

CorderSchema

DDocument

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Document' instead of 'Schema'.

Passing the model name instead of the schema to mongoose.model.

We define the schema with Schema, create the model with model, and pass the schema variable orderSchema.

Practice

1. What is the main purpose of defining a model in an Express app using Mongoose?

easy

A. To style the app with CSS

B. To define the structure and rules for data stored in the database

C. To handle HTTP requests and responses

D. To create the user interface of the app

Solution

1. Step 1: Understand what a model represents

   A model defines how data is structured and validated in the database.

2. Step 2: Identify the role of models in Express apps

   Models help manage data and enforce rules before saving to the database.

3. Final Answer:

   To define the structure and rules for data stored in the database -> Option B

4. Quick Check:

   Model = Data structure and rules [OK]

Hint: Models define data shape and rules, not UI or styling [OK]

Common Mistakes:

• Confusing models with UI components
• Thinking models handle HTTP requests
• Assuming models style the app

2. Which of the following is the correct way to define a Mongoose model named Book with a schema having a title field of type String?

easy

A. const Book = mongoose.model('Book', new mongoose.Schema({ title: String }));

B. const Book = mongoose.schema('Book', { title: String });

C. const Book = mongoose.model('Book', { title: String });

D. const Book = new mongoose.model('Book', { title: String });

Solution

1. Step 1: Recall Mongoose model syntax

   Mongoose models require a schema object created with new mongoose.Schema().

2. Step 2: Check each option for correct usage

   const Book = mongoose.model('Book', new mongoose.Schema({ title: String })); correctly uses mongoose.model('Book', new mongoose.Schema({ title: String })). Others misuse schema or omit new mongoose.Schema().

3. Final Answer:

   const Book = mongoose.model('Book', new mongoose.Schema({ title: String })); -> Option A

4. Quick Check:

   Model needs new Schema() [OK]

Hint: Use new mongoose.Schema() inside mongoose.model() [OK]

Common Mistakes:

• Using mongoose.schema instead of new Schema()
• Passing plain object instead of Schema instance
• Using new keyword incorrectly with mongoose.model

3. Given the following code, what will console.log(book.title) output?

const mongoose = require('mongoose');
const { Schema } = mongoose;

const bookSchema = new Schema({ title: String });
const Book = mongoose.model('Book', bookSchema);

const book = new Book({ title: 'Express Guide' });
console.log(book.title);

medium

A. Error: book.title is not defined

B. undefined

C. 'Express Guide'

D. null

Solution

1. Step 1: Understand model instance creation

   Creating new Book({ title: 'Express Guide' }) sets the title property on the instance.

2. Step 2: Access the title property

   Logging book.title outputs the string 'Express Guide' as assigned.

3. Final Answer:

   'Express Guide' -> Option C

4. Quick Check:

   Instance property = 'Express Guide' [OK]

Hint: Instance properties match schema fields given at creation [OK]

Common Mistakes:

• Expecting undefined because of missing database save
• Confusing model with schema
• Thinking title is a method, not a property

4. Identify the error in this model definition code:

const mongoose = require('mongoose');
const bookSchema = mongoose.Schema({ title: String });
const Book = mongoose.model('Book', bookSchema);

const book = new Book({ title: 123 });

medium

A. Schema should be created with new Schema(), not mongoose.Schema()

B. Missing call to connect to the database before defining model

C. Model name 'Book' must be lowercase

D. The title field value should be a string, not a number

Solution

1. Step 1: Check schema field types and values

   The schema defines title as a String, but the instance is created with a number 123.

2. Step 2: Identify type mismatch error

   Mongoose expects a string for title, so passing a number is a validation error.

3. Final Answer:

   The title field value should be a string, not a number -> Option D

4. Quick Check:

   Schema type mismatch causes error [OK]

Hint: Match data types in schema and instance exactly [OK]

Common Mistakes:

• Ignoring type mismatch errors
• Thinking model names must be lowercase
• Confusing schema creation syntax

5. You want to define a Mongoose model User with fields name (string), age (number), and email (string, required). Which code correctly defines this model with validation?

hard

A. const userSchema = new mongoose.Schema({ name: String, age: Number, email: { type: String, required: true } }); const User = mongoose.model('User', userSchema);

B. const userSchema = new Schema({ name: String, age: Number, email: String, required: true }); const User = mongoose.model('User', userSchema);

C. const userSchema = new Schema({ name: String, age: Number, email: String }); const User = mongoose.model('User', userSchema, { required: ['email'] });

D. const userSchema = new Schema({ name: String, age: Number, email: { type: String } }); const User = mongoose.model('User', userSchema);

Solution

1. Step 1: Understand how to set required fields in schema

   Required fields must be defined inside the field object with required: true.

2. Step 2: Check each option for correct required syntax

   const userSchema = new mongoose.Schema({ name: String, age: Number, email: { type: String, required: true } }); const User = mongoose.model('User', userSchema); correctly sets email: { type: String, required: true }. Others either place required outside the field or omit it.

3. Final Answer:

   const userSchema = new mongoose.Schema({ name: String, age: Number, email: { type: String, required: true } }); const User = mongoose.model('User', userSchema); -> Option A

4. Quick Check:

   Required fields inside field object [OK]

Hint: Put required: true inside the field's object definition [OK]

Common Mistakes:

• Placing required outside the field object
• Omitting required for mandatory fields
• Misusing model options for validation