Master the IT-English vocabulary of partitioning and sharding: shard keys, hotspots, horizontal partitioning and rebalancing.
0 / 14 completed
1 / 14
What is 'sharding' a database?
Sharding horizontally partitions data across servers so each holds part of the dataset.
2 / 14
A poorly chosen 'shard key' causes a 'hotspot'. What is a hotspot?
A hotspot is uneven distribution where one shard is overloaded while others sit idle.
3 / 14
'Horizontal partitioning' splits a table how?
Horizontal partitioning divides rows across partitions; vertical partitioning splits columns.
4 / 14
After adding a node the cluster 'rebalances'. What does that mean?
Rebalancing moves data so the new capacity is used and no node is overloaded.
5 / 14
Which sentence correctly uses 'cross-shard query'?
Cross-shard queries span multiple shards and are costlier, so shard keys are chosen to minimise them.
6 / 14
Reviewer: 'I noticed a high latency on queries involving the user's order history. It seems like we're consistently hitting the same table shard for all users. This could indicate a problem with our sharding strategy.'
What is the reviewer *primarily* concerned about regarding this observed latency?
The reviewer's comment directly addresses the issue of a 'hotspot,' which occurs when a particular shard receives an disproportionately large amount of query traffic. While resource constraints and inefficient code can contribute to latency, the core problem identified here is related to the data distribution across shards – specifically, that the shard key isn't diverse enough. The incorrect options focus on unrelated issues or assume normal performance behavior without investigating the underlying cause of the high load.
7 / 14
Reviewer: 'I noticed a high latency on queries involving the user's order history. It seems like we're consistently hitting the same table shard for all users. This could indicate a problem with our sharding strategy.'
What is the reviewer *primarily* concerned about regarding this observed latency?
The reviewer's comment directly addresses the issue of a 'hotspot,' which occurs when a particular shard receives an disproportionately large amount of query traffic. While resource constraints and inefficient code can contribute to latency, the core problem identified here is related to the data distribution across shards – specifically, that the shard key isn't diverse enough. The incorrect options focus on unrelated issues or assume normal performance behavior without investigating the underlying cause of the high load.
8 / 14
Reviewer: 'I noticed a high latency on queries involving the user's order history. It seems like we're consistently hitting the same table shard for all users. This could indicate a problem with our sharding strategy.'
What is the reviewer *primarily* concerned about regarding this observed latency?
The reviewer's comment directly addresses the issue of a 'hotspot,' which occurs when a particular shard receives an disproportionately large amount of query traffic. While resource constraints and inefficient code can contribute to latency, the core problem identified here is related to the data distribution across shards – specifically, that the shard key isn't diverse enough. The incorrect options focus on unrelated issues or assume normal performance behavior without investigating the underlying cause of the high load.
9 / 14
Reviewer: 'I noticed a high latency on queries involving the user's order history. It seems like we're consistently hitting the same table shard for all users. This could indicate a problem with our sharding strategy.'
What is the reviewer *primarily* concerned about regarding this observed latency?
The reviewer's comment directly addresses the issue of a 'hotspot,' which occurs when a particular shard receives an disproportionately large amount of query traffic. While resource constraints and inefficient code can contribute to latency, the core problem identified here is related to the data distribution across shards – specifically, that the shard key isn't diverse enough. The incorrect options focus on unrelated issues or assume normal performance behavior without investigating the underlying cause of the high load.
10 / 14
Reviewer: 'The application's performance is suffering. Specifically, queries retrieving user profile data are experiencing significant delays. Initial investigation suggests a potential bottleneck related to our sharding implementation. Can you elaborate on how the user profiles are currently distributed across shards?'
This question assesses understanding of hotspot mitigation through shard key selection. Option A addresses query optimization, not sharding itself. Option C focuses on network issues, which are secondary to the core problem. Incorrectly choosing a shard key (like just user ID) can lead to uneven distribution and hotspots; option B correctly identifies this crucial consideration.
11 / 14
Slack Message: 'Hey team, we're seeing a lot of complaints about slow loading times for product catalog searches. The system is using a hash function on the product ID to determine which shard holds the data. I think it's time to revisit our sharding strategy.' What does 'hash function' refer to in this context?
The question tests the understanding of how hash functions are utilized in sharding. Option A describes encryption, which is unrelated. Option C refers to a command-line tool and option D represents indexing. The core concept of sharding involves mapping data based on a function – hence, 'hash function' correctly identifies the role.
12 / 14
PR Description: 'Implemented cross-shard query support using the new `JOIN ... CROSS SHARD` syntax. This allows us to retrieve data from multiple shards in a single query, improving performance for complex reporting needs.' What is the *primary* benefit of utilizing 'cross-shard queries'?
This question focuses on the practical impact of cross-shard queries. While they improve performance through reduced network traffic (option C is partially true), the *primary* benefit isn't eliminating sharding or automatically fixing imbalances; it's about efficiently accessing data spread across shards. Option A and B are incorrect because cross-shard queries don't replace sharding.
13 / 14
Standup Update: 'Yesterday, we added a new node to the database cluster. The system is currently rebalancing data across shards to ensure optimal performance and resource utilization.' What does 'rebalancing' mean in this context?
The question directly probes understanding of the rebalancing process after adding a node. 'Rebalancing' describes the dynamic process of redistributing data – it's not a full rebuild (A) or complete shutdown (C). It involves shifting data to maintain balance based on changing conditions, which is option B.
14 / 14
API Response: The database server returned the following error message: 'Shard conflict detected during cross-shard transaction. Transaction rolled back.' What is the most likely cause of this error?
This question tests understanding of a common sharding-related error. 'Shard conflict' arises when concurrent updates happen on different shards referencing the same data – option A directly explains this scenario. Options B and C describe other potential issues, while option D refers to an incorrect shard key configuration (which would cause errors but not necessarily a 'conflict').
What does the "Partitioning & Sharding Language" exercise practise?
Master the IT-English vocabulary of partitioning and sharding: shard keys, hotspots, horizontal partitioning and rebalancing.
How many questions are in this exercise?
This exercise has 14 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Database Optimization category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Partitioning & Sharding Language" part of a larger series?
Yes — it's one exercise in the Database Optimization category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Database Optimization category page for related exercises, or browse the main Exercises hub for other IT English topics.