Okay, I've got a strategy here. I'll think about the pros and cons of sharding in each of these situations and try to determine which ones would not benefit from it.
Hmm, this is a tricky one. I'm not entirely sure about the details of when sharding is appropriate, but I'll try to reason through the scenarios and make my best guess.
The key seems to be identifying the characteristics of the collection that would make sharding not the right choice. I'll need to carefully consider the options and think about the trade-offs.
This question is asking about when sharding is not the correct option. I think I need to focus on understanding the different scenarios and how they relate to the decision to shard or not.
I'm pretty sure B and C are the correct answers here. Sharding is all about scaling out your database, so low write ops and read-heavy workloads don't really need that kind of heavy-duty solution.
Haha, I bet the exam writers were trying to trick us with these options. 'Very high write operations' and 'very large working set'? Sounds like a job for sharding if you ask me!
Wait, what? Sharding is not the correct option for low write operations? That's a head-scratcher. I guess I need to review my sharding fundamentals again.
Hmm, I think B and C are the correct answers here. Sharding is meant to handle high write operations and growing data sets, so those scenarios wouldn't be a good fit for sharding.
Carlota
6 months agoVal
6 months agoVerlene
6 months agoPete
7 months agoDorothea
7 months agoPortia
7 months agoMatthew
7 months agoRosina
7 months agoJustine
8 months agoCyril
8 months agoIzetta
8 months agoParis
8 months agoGiovanna
8 months agoJesusa
1 year agoCelestine
1 year agoLaquita
12 months agoMozell
12 months agoGalen
1 year agoMillie
12 months agoJade
1 year agoNickolas
1 year agoTu
1 year agoRaul
1 year agoSena
1 year agoLanie
1 year agoSanda
1 year agoCammy
1 year agoLatrice
1 year ago