Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/MongoDB
MongoDBmedium

What is a covered query in MongoDB and why can it be faster?

Tags
#mongo#indexes#covered-query#performance
Back to categoryPractice quiz

Answer

A covered query can be answered using only an index, without fetching the full document. It can be faster because it avoids reading documents from disk/memory. You get it when the filter and the returned fields are all in the same index (and you don’t need any other fields).

db.users.createIndex({ email: 1, createdAt: 1 })

// Only indexed fields are returned => can be covered
db.users.find({ email: "[email protected]" }, { _id: 0, email: 1, createdAt: 1 })

Related questions

MongoDB
Unique vs sparse vs partial indexes: what’s the difference?
#mongo#indexes#unique
MongoDB
Text indexes: when would you use them and what’s a limitation?
#mongo#text-index#search
MongoDB
`$lookup`: what does it do and what is a common pitfall?
#mongo#lookup#aggregation
MongoDB
Replica set elections: what happens during an election?
#mongo#replica-set#election
MongoDB
Read preference in replica sets: what does `primary` vs `secondary` mean?
#mongo#replica-set#read-preference
MongoDB
Read concern vs write concern: what do they control?
#mongo#consistency#read-concern