Bird
Raised Fist0
MongoDBquery~30 mins

Mongos router behavior in MongoDB - Mini Project: Build & Apply

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Understanding Mongos Router Behavior in MongoDB
📖 Scenario: You are managing a MongoDB sharded cluster for an online bookstore. The cluster uses a mongos router to direct queries to the correct shards. You want to understand how mongos routes queries and manages data distribution.
🎯 Goal: Build a simple MongoDB setup with a sharded collection and use mongos to query data. Learn how mongos routes queries to shards based on shard keys.
📋 What You'll Learn
Create a sharded collection with a shard key
Enable sharding on the database
Insert sample documents into the collection
Query the collection through the mongos router
💡 Why This Matters
🌍 Real World
Sharded MongoDB clusters are used in real-world applications to scale databases horizontally and distribute data across multiple servers for better performance and availability.
💼 Career
Understanding mongos router behavior is essential for database administrators and backend developers working with large-scale MongoDB deployments to optimize query performance and data distribution.
Progress0 / 4 steps
1
Enable sharding on the bookstore database
Use the sh.enableSharding() command to enable sharding on the database named bookstore.
MongoDB
Hint

Use sh.enableSharding("bookstore") to enable sharding on the database.

2
Shard the books collection on the isbn field
Use the sh.shardCollection() command to shard the collection books in the bookstore database on the isbn field.
MongoDB
Hint

Use sh.shardCollection("bookstore.books", { isbn: 1 }) to shard the collection on the isbn field.

3
Insert sample book documents into the books collection
Insert three documents into the books collection with these exact fields and values: { isbn: "978-0132350884", title: "Clean Code", author: "Robert C. Martin" }, { isbn: "978-0201616224", title: "The Pragmatic Programmer", author: "Andrew Hunt" }, and { isbn: "978-0131103627", title: "The C Programming Language", author: "Brian W. Kernighan" }.
MongoDB
Hint

Use db.books.insertMany([...]) with the exact documents to insert multiple books.

4
Query the books collection for a book by isbn using mongos
Write a query using db.books.find() to find the document where isbn is "978-0201616224". This query will be routed by mongos to the correct shard.
MongoDB
Hint

Use db.books.find({ isbn: "978-0201616224" }) to query the book by its ISBN.

Practice

(1/5)
1. What is the primary role of the mongos router in a sharded MongoDB cluster?
easy
A. It stores the actual data for the database.
B. It routes queries to the correct shard based on the shard key.
C. It manages user authentication and roles.
D. It backs up the database automatically.

Solution

  1. Step 1: Understand mongos role

    The mongos acts as a query router in a sharded cluster, directing queries to the right shard.

  2. Step 2: Differentiate from other components

    Data storage is handled by shards, not mongos. Authentication and backups are separate concerns.

  3. Final Answer:

    It routes queries to the correct shard based on the shard key. -> Option B

  4. Quick Check:

    mongos routes queries [OK]
Hint: Remember: mongos routes, shards store data [OK]
Common Mistakes:
  • Thinking mongos stores data
  • Confusing mongos with config servers
  • Assuming mongos handles backups
2. Which of the following is the correct way for an application to connect in a sharded MongoDB setup?
easy
A. Connect to the primary replica set member.
B. Connect only to the config servers.
C. Connect directly to each shard individually.
D. Connect to the mongos router.

Solution

  1. Step 1: Identify connection point in sharded cluster

    Applications connect to mongos which routes queries to shards transparently.

  2. Step 2: Exclude other options

    Direct connection to shards or config servers is not recommended; primary replica set member is for replica sets, not sharding.

  3. Final Answer:

    Connect to the mongos router. -> Option D

  4. Quick Check:

    Apps connect to mongos [OK]
Hint: Always connect apps to mongos, not shards [OK]
Common Mistakes:
  • Connecting directly to shards
  • Using config servers for queries
  • Confusing replica sets with sharding
3. Given a sharded cluster with two shards and a mongos router, what will happen when you run this query through mongos? 
db.users.find({ userId: 12345 })
Assume userId is the shard key.
medium
A. mongos returns an error because shard key is missing.
B. mongos sends the query to all shards and merges results.
C. mongos routes the query only to the shard containing userId 12345.
D. mongos sends the query to the config servers.

Solution

  1. Step 1: Check query uses shard key

    The query filters on userId, which is the shard key, so mongos can route precisely.

  2. Step 2: Understand mongos routing behavior

    mongos sends the query only to the shard that holds the chunk for userId 12345, not all shards.

  3. Final Answer:

    mongos routes the query only to the shard containing userId 12345. -> Option C

  4. Quick Check:

    Query with shard key routes to one shard [OK]
Hint: Query with shard key goes to one shard only [OK]
Common Mistakes:
  • Assuming mongos queries all shards always
  • Thinking config servers handle queries
  • Believing shard key is optional for routing
4. You wrote a query to find documents by userId in a sharded cluster but get slow results. You realize userId is not the shard key. What is the likely cause?
medium
A. mongos is routing the query to all shards (scatter-gather).
B. mongos is routing the query to only one shard.
C. mongos is ignoring the query and returning empty results.
D. mongos is connecting directly to config servers.

Solution

  1. Step 1: Identify shard key usage in query

    The query filters on userId, which is not the shard key, so mongos cannot route precisely.

  2. Step 2: Understand mongos scatter-gather behavior

    mongos sends the query to all shards (scatter-gather) causing slower results.

  3. Final Answer:

    mongos is routing the query to all shards (scatter-gather). -> Option A

  4. Quick Check:

    Query without shard key causes scatter-gather [OK]
Hint: Queries without shard key hit all shards, slowing response [OK]
Common Mistakes:
  • Assuming query routes to one shard without shard key
  • Thinking mongos returns empty results on missing shard key
  • Confusing config servers with query routers
5. In a sharded MongoDB cluster, you want to optimize query performance for a collection frequently queried by email. The current shard key is userId. What is the best approach involving mongos behavior?
hard
A. Change the shard key to email so mongos routes queries efficiently.
B. Add an index on email and keep the shard key as userId.
C. Connect directly to shards to bypass mongos routing.
D. Disable sharding on the collection to improve query speed.

Solution

  1. Step 1: Analyze query pattern and shard key

    Queries are frequent on email, but shard key is userId, causing scatter-gather queries via mongos.

  2. Step 2: Optimize shard key for routing

    Changing shard key to email lets mongos route queries directly to relevant shards, improving performance.

  3. Final Answer:

    Change the shard key to email so mongos routes queries efficiently. -> Option A

  4. Quick Check:

    Shard key matches query field for efficient mongos routing [OK]
Hint: Match shard key to frequent query field for fast mongos routing [OK]
Common Mistakes:
  • Thinking adding index alone fixes routing
  • Connecting directly to shards bypasses mongos is not recommended
  • Disabling sharding reduces scalability
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard