Why sharding is needed in MongoDB - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to show the main reason for sharding in MongoDB.

MongoDB

Sharding is used to [1] data across multiple servers to handle large datasets.

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

Adelete

Bcombine

Csplit

Dbackup

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'combine' because it sounds like joining data.

Sharding means splitting data across servers to manage large amounts efficiently.

2fill in blank

medium

Complete the code to explain what problem sharding solves.

MongoDB

Sharding helps to [1] the load and storage so the database can scale horizontally.

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

Aincrease

Bdistribute

Cignore

Dreduce

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'increase' thinking more load is good.

Sharding distributes load and storage across servers to scale the database.

3fill in blank

hard

Fix the error in the sentence about sharding's benefit.

MongoDB

Sharding allows multiple servers to handle [1] data efficiently.

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

Asmall

Bno

Call

Dlarge

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'small' because it sounds easier to handle.

Sharding helps handle large data by spreading it across servers, not small data.

4fill in blank

hard

Fill both blanks to complete the explanation of sharding.

MongoDB

Sharding improves [1] by splitting data and [2] by adding more servers.

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

Aperformance

Bsecurity

Cscalability

Dbackup

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing security or backup with sharding benefits.

Sharding improves performance and scalability by splitting data and adding servers.

5fill in blank

hard

Fill all three blanks to describe sharding benefits.

MongoDB

Sharding [1] data, [2] load, and [3] database capacity.

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

Adistributes

Breduces

Cincreases

Ddeletes

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'deletes' which is incorrect for sharding.

Sharding distributes data, reduces load on each server, and increases overall capacity.

Practice

1. Why is sharding needed in MongoDB?

easy

A. To split large data across multiple servers for better performance

B. To backup data automatically

C. To encrypt data for security

D. To create indexes on collections

Solution

1. Step 1: Understand the purpose of sharding

   Sharding divides large datasets into smaller parts stored on different servers.

2. Step 2: Identify the benefit of sharding

   This division helps the database handle more data and users efficiently.

3. Final Answer:

   To split large data across multiple servers for better performance -> Option A

4. Quick Check:

   Sharding = splitting data for speed [OK]

Hint: Sharding means splitting data to keep speed fast [OK]

Common Mistakes:

• Confusing sharding with backup
• Thinking sharding is for security
• Mixing sharding with indexing

2. Which of the following is the correct way to enable sharding on a database named mydb in MongoDB shell?

easy

A. sh.enableSharding('mydb')

B. db.enableSharding('mydb')

C. sh.shardEnable('mydb')

D. enableSharding('mydb')

Solution

1. Step 1: Recall the MongoDB shell command for enabling sharding

   The correct command uses the sh object with enableSharding() method.

2. Step 2: Match the correct syntax

   Only sh.enableSharding('mydb') matches the official syntax.

3. Final Answer:

   sh.enableSharding('mydb') -> Option A

4. Quick Check:

   sh.enableSharding() is correct syntax [OK]

Hint: Use sh.enableSharding('dbName') to enable sharding [OK]

Common Mistakes:

• Using db instead of sh
• Wrong method name like shardEnable
• Calling enableSharding without sh prefix

3. Consider a MongoDB cluster with sharding enabled. If a collection is not sharded, what happens when data grows very large?

medium

A. The data is automatically split across shards

B. All data stays on a single server, causing slow queries

C. MongoDB deletes old data to save space

D. The cluster crashes immediately

Solution

1. Step 1: Understand sharding effect on collections

   Only sharded collections split data across servers; unsharded collections stay on one server.

2. Step 2: Predict behavior when data grows large

   Large unsharded collections cause slow queries because one server handles all data.

3. Final Answer:

   All data stays on a single server, causing slow queries -> Option B

4. Quick Check:

   Unsharded = single server, slow queries [OK]

Hint: Unsharded data stays on one server, slowing queries [OK]

Common Mistakes:

• Assuming data auto-splits without sharding
• Thinking MongoDB deletes data automatically
• Believing cluster crashes immediately

4. You tried to shard a collection but got an error: "shard key not found". What is the likely cause?

medium

A. Sharding is not enabled on the cluster

B. The collection is empty

C. You used the wrong database name

D. You did not create an index on the shard key field

Solution

1. Step 1: Understand shard key requirements

   MongoDB requires an index on the shard key field before sharding a collection.

2. Step 2: Identify cause of error

   The error "shard key not found" usually means the shard key field lacks an index.

3. Final Answer:

   You did not create an index on the shard key field -> Option D

4. Quick Check:

   Shard key needs index [OK]

Hint: Shard key must have an index before sharding [OK]

Common Mistakes:

• Ignoring index creation on shard key
• Assuming empty collection causes error
• Confusing database name with shard key

5. A company has a MongoDB database with a collection growing rapidly. They want to keep queries fast and handle many users. Which approach best uses sharding to solve this?

hard

A. Do not shard and increase RAM on the single server

B. Shard the collection using a field with few unique values

C. Shard the collection using a field with high cardinality and evenly distributed values

D. Shard the collection randomly without a shard key

Solution

1. Step 1: Identify good shard key characteristics

   A good shard key has many unique values (high cardinality) and distributes data evenly.

2. Step 2: Evaluate options for sharding

   Using a field with few unique values causes unbalanced shards; random sharding is not possible without a shard key.

3. Step 3: Consider scaling alternatives

   Increasing RAM alone won't handle very large data or many users efficiently.

4. Final Answer:

   Shard the collection using a field with high cardinality and evenly distributed values -> Option C

5. Quick Check:

   Good shard key = high cardinality, even distribution [OK]

Hint: Choose shard key with many unique, evenly spread values [OK]

Common Mistakes:

• Picking shard key with few unique values
• Trying to shard without a shard key
• Relying only on hardware upgrades