Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

MongoDB C100DBA Exam - Topic 6 Question 100 Discussion

In which of the following scenarios is sharding not the correct option. Select all that apply.
C) The working set in the collection is expected to grow very large in size
A) The write operations on the collection are low
B) The write operations on the collection are very high
D) The collection is a read intensive collection with less working set

MongoDB C100DBA Exam - Topic 6 Question 100 Discussion

Actual exam question for MongoDB's C100DBA exam
Question #: 100
Topic #: 6
[All C100DBA Questions]

In which of the following scenarios is sharding not the correct option. Select all that apply.

Show Suggested Answer Hide Answer
Suggested Answer: C

by Hana at Sep 16, 2024, 09:17 AM

Limited Time Offer

25%

Off

Get Premium C100DBA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Carlota
7 months ago
I'm not so sure about D, can someone explain?
upvoted 0 times
...
Val
8 months ago
B and C are where sharding shines, for sure.
upvoted 0 times
...
Verlene
8 months ago
Wait, isn't sharding supposed to help with large datasets?
upvoted 0 times
...
Pete
8 months ago
Totally agree, D makes sense too!
upvoted 0 times
...
Dorothea
8 months ago
A is definitely not a good reason for sharding.
upvoted 0 times
...
Portia
9 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.
upvoted 0 times
...
Matthew
9 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.
upvoted 0 times
...
Rosina
9 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.
upvoted 0 times
...
Justine
9 months ago
I think sharding isn't necessary when write operations are low, so maybe A? But I'm not entirely sure.
upvoted 0 times
...
Cyril
9 months 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.
upvoted 0 times
...
Izetta
9 months 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.
upvoted 0 times
...
Paris
9 months 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.
upvoted 0 times
...
Giovanna
9 months 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.
upvoted 0 times
...
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.
upvoted 0 times
...
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!
upvoted 0 times
Laquita
1 year ago
C) The working set in the collection is expected to grow very large in size
upvoted 0 times
...
Mozell
1 year ago
A) The write operations on the collection are low
upvoted 0 times
...
...
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.
upvoted 0 times
Millie
1 year ago
C) The working set in the collection is expected to grow very large in size
upvoted 0 times
...
Jade
1 year ago
B) The write operations on the collection are very high
upvoted 0 times
...
Nickolas
1 year ago
A) The write operations on the collection are low
upvoted 0 times
...
...
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!
upvoted 0 times
...
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?
upvoted 0 times
...
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.
upvoted 0 times
Lanie
1 year ago
Sharding is more suitable for scenarios with high write operations and large working sets.
upvoted 0 times
...
Sanda
1 year ago
I agree, B and C are not the correct scenarios for sharding.
upvoted 0 times
...
...
Cammy
1 year ago
I agree with Latrice. Sharding is meant to improve write scalability, so it's not necessary when the write operations are low.
upvoted 0 times
...
Latrice
1 year ago
I think sharding is not the correct option when the write operations are low.
upvoted 0 times
...

Save Cancel