Chunks and balancer concept in MongoDB - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary role of chunks in MongoDB sharding?

In MongoDB sharding, data is split into smaller parts called chunks. What is the main purpose of these chunks?

A To create indexes on collections

B To backup data automatically in the cluster

C To encrypt data before storing it

D To divide data into manageable pieces for distribution across shards

💡 Hint

Think about how data is shared across multiple servers.

Chunks split the data into smaller parts so MongoDB can spread them across different servers (shards). This helps balance the load and store large datasets efficiently.

❓ query_result

intermediate

What does the balancer do in a MongoDB sharded cluster?

Consider a MongoDB sharded cluster where chunks are unevenly distributed. What is the balancer's role in this scenario?

A Moves chunks between shards to keep data evenly distributed

B Deletes old chunks to free up space

C Creates new chunks automatically when data grows

D Merges all chunks into a single shard

💡 Hint

Think about how the system keeps the data balanced across servers.

The balancer moves chunks from busy shards to less busy ones to keep the data spread evenly. This helps maintain performance and storage balance.

📝 Syntax

advanced

Which MongoDB command shows the current chunk distribution across shards?

You want to check how chunks are distributed in your sharded cluster. Which command will give you this information?

A sh.getBalancerState()

B db.chunks.find()

C sh.status()

D db.shards.find()

💡 Hint

Look for the command that gives an overview of the sharding setup.

sh.status() shows detailed information about shards, databases, collections, and chunk distribution in the cluster.

🔧 Debug

advanced

Why might the balancer not move chunks even if data is uneven?

In a sharded cluster, the balancer is enabled but chunks are not moving to balance data. Which of the following is a likely cause?

A The shard key is not defined

B The balancer is paused or locked due to ongoing migrations

C Chunks are too large and cannot be split further

D The cluster has only one shard

💡 Hint

Think about what might temporarily stop the balancer from working.

The balancer can be paused or locked during chunk migrations or maintenance, preventing it from moving chunks even if data is uneven.

❓ optimization

expert

How can you optimize chunk size to improve balancer efficiency?

You notice the balancer is moving chunks too frequently, causing overhead. What is a good way to optimize chunk size for better balancer performance?

A Increase the chunk size to reduce the number of chunks

B Decrease the chunk size to create more chunks

C Disable the balancer permanently

D Remove the shard key from the collection

💡 Hint

Think about how chunk size affects how often chunks move.

Larger chunks mean fewer chunks overall, so the balancer moves chunks less often, reducing overhead and improving cluster performance.