You have now learned the basic vocabulary and mental model required for the rest of the course.

Before moving forward, make sure you can explain the following concepts without relying on memorized definitions:

• Why MongoDB is described as a document database.
• How deployments, databases, collections, and documents relate to one another.
• How arrays and embedded documents represent structured application data.
• Why BSON is different from plain JSON.
• Why a flexible schema does not remove the need for validation.
• How to connect to a deployment using mongosh.
• How to insert documents and retrieve them with find().
• How to filter on a nested field using dot notation.
• How a projection changes the returned fields.
• Why document growth and access patterns matter to data modeling.

Readiness exercise

Create a collection called students with at least four documents. Each document should contain a name, a numeric age, an array of enrolled subjects, and a nested address document. Include at least one optional field, such as scholarship or graduationYear.

Then write queries to:

1. Retrieve all students.
2. Find students older than 20.
3. Find students enrolled in Mathematics.
4. Find students from a particular city using dot notation.
5. Return only student names and ages.
6. Find documents where the optional field does not exist.

Finally, explain what might happen if different application services store ages as different BSON types.

What comes next

The next chapter should focus on MongoDB installation, deployment setup, connection strings, mongosh configuration, database and collection creation, and a repeatable development environment. This will establish the foundation for the CRUD operations and querying chapters that follow.