Technologies Coding Problems Bookmarks Learning Paths

Technologies Coding Problems Bookmarks Learning Paths

AI-powered interview preparation platform. Practice with curated questions, mock interviews, and personalized learning paths to crack your dream tech interview.

Quick Links

Technologies
Saved Questions
Pricing

Company

About Us
Contact Us

Legal

Privacy Policy
Terms of Use

© 2026 nextRound. All rights reserved.

Questions

13 of 15

1How to find a shard key?

2What is refining a shard key and how to do it?

3How to reshard a collection?

4What are different sharding strategies?

5What is Shard?

6What are advantages of Sharding?

7What are the components of a sharded cluster?

8Discuss Vertical and Horizontal scaling?

9What is sharding in MongoDB?

10How to shard a collection?

11What is a shard key?

12How do we chose a shard key?

13What are zones in sharding?

14Is it possible to change a document's shard key value and how?

15What is primary shard?

MongoDB

Bulk Operations

13 / 15

What are zones in sharding? | Sharding | MongoDB Interview Questions | NextRound.in

What are zones in sharding?

Difficulty: 5/10

shard zones, data placement, balancer

Zone is a grouping of documents based on ranges of shard key values for a given sharded collection. zones are logical groupings of shards based on specific criteria, such as geographical location or data type. Each shard in the sharded cluster can be in one or more zones. In a balanced cluster, MongoDB directs reads and writes for a zone only to those shards inside that zone. See the Zones manual page for more information.

1
Geographic Zones: Data is distributed into shards based on regions, ensuring users in Asia primarily interact with servers in Asia, minimizing access delays.
2
Functional Zones: Shards are grouped based on application-specific logic, such as separating user data from transaction data.

Scenario Questions

0-2 years experience

1If you need to ensure that all orders from Europe are stored on a specific shard, how would you configure zones in MongoDB?
2What happens when you add a new zone range that overlaps with an existing one? How does the balancer react?
3Suppose you have a collection sharded on 'userId' and you want to keep IDs 0‑999 on shard A and the rest on shard B. Walk me through the steps to set that up.

Follow-up Questions

Can you walk me through how the balancer decides which chunk to move for a zone?
What metrics would you watch to know a zone is becoming imbalanced?
How would you test your zone configuration before rolling it out to production?

Sharethis question

Share via WhatsApp, X, Facebook, LinkedIn or copy link. Open Graph preview enabled.

2-5 years experience

1Your application is experiencing latency spikes because the balancer is moving chunks across zones during peak hours. How would you diagnose and mitigate the issue?
2We decided to add a new data‑center in Asia and want to create a zone for that region. What trade‑offs do you consider when assigning chunk ranges to the new shard?
3During a deployment, you notice that a zone you defined is not receiving any chunks. What could cause this and how would you fix it?

5-8 years experience

1Design a strategy to automatically rebalance zones when a shard becomes overloaded, ensuring minimal impact on read/write latency.
2Explain how you would handle a scenario where regulatory requirements force you to move a specific key range from one zone to another without downtime.
3What are the performance implications of having many small zones versus a few large zones, and how would you decide the granularity?

8+ years experience

1At a company with multiple microservices each owning different data domains, how would you architect zone definitions to support cross‑service data locality while allowing independent team ownership?
2If you need to migrate a legacy monolithic MongoDB deployment to a sharded cluster with zones, outline the migration plan, including data back‑fill, zone rollout, and rollback considerations.
3Discuss the long‑term operational challenges of maintaining zone configurations as the business evolves, and propose governance processes to keep them aligned.