MENU
In which of the following scenarios is sharding not the correct option. Select all that apply.
Suggested Answer: C
Get Premium C100DBA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
28 comments · newest first
CA
Carlota
10 months ago
I'm not so sure about D, can someone explain?
VA
Val
11 months ago
B and C are where sharding shines, for sure.
VE
Verlene
11 months ago
Wait, isn't sharding supposed to help with large datasets?
PE
Pete
11 months ago
Totally agree, D makes sense too!
DO
Dorothea
11 months ago
A is definitely not a good reason for sharding.
PO
Portia
12 months ago
I agree with Justine about A, but I also feel like D makes sense since sharding might complicate things for read-heavy scenarios.
MA
Matthew
12 months ago
I’m a bit confused about C. If the working set grows large, wouldn’t sharding help? I need to think this through more.
RO
Rosina
12 months ago
I remember practicing a question where sharding was not recommended for read-intensive collections, so I feel like D could be a correct answer too.
JU
Justine
1 year ago
I think sharding isn't necessary when write operations are low, so maybe A? But I'm not entirely sure.
CY
Cyril
1 year ago
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.
IZ
Izetta
1 year ago
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.
PA
Paris
1 year ago
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.
GI
Giovanna
1 year ago
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.
JE
Jesusa
1 year ago
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.
CE
Celestine
1 year ago
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!
LA
Laquita
1 year ago
C) The working set in the collection is expected to grow very large in size
MO
Mozell
1 year ago
A) The write operations on the collection are low
GA
Galen
1 year ago
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.
MI
Millie
1 year ago
C) The working set in the collection is expected to grow very large in size
JA
Jade
1 year ago
B) The write operations on the collection are very high
NI
Nickolas
1 year ago
A) The write operations on the collection are low
TU
Tu
1 year ago
I agree with Sena. Plus, D is a read-intensive collection, and sharding is a great option for that use case. Gotta love those MongoDB tricks!
RA
Raul
1 year ago
But what about when the working set is expected to grow very large in size? Wouldn't sharding still be beneficial in that scenario?
SE
Sena
1 year ago
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.
LA
Lanie
1 year ago
Sharding is more suitable for scenarios with high write operations and large working sets.
SA
Sanda
1 year ago
I agree, B and C are not the correct scenarios for sharding.
CA
Cammy
2 years ago
I agree with Latrice. Sharding is meant to improve write scalability, so it's not necessary when the write operations are low.
LA
Latrice
2 years ago
I think sharding is not the correct option when the write operations are low.