MENU
When should we consider representing a one-to-many relationship in an embedded collection instead of separate collection?
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
42 comments · newest first
ME
Merlyn
10 months ago
Wait, are we really saying "always"? That sounds risky!
ED
Edna
11 months ago
Never? D seems too extreme, there are exceptions!
PA
Patti
11 months ago
Always use embedded collections, C is the best!
ER
Ernie
11 months ago
I disagree, B makes more sense for large datasets.
RO
Rosalind
11 months ago
A is definitely the way to go when the many is small.
CA
Carline
12 months ago
I think the answer is definitely not always or never, but I can't remember the exact scenarios for embedded collections.
KE
Kenneth
12 months ago
I feel like the answer could be option A, but I also recall something about performance issues with large datasets.
GL
Glory
12 months ago
I remember practicing a question where it mentioned that large collections might be better off in separate collections, so I’m leaning towards option B.
LA
Lai
1 year ago
I think we should use an embedded collection when the many is not very large, but I'm not entirely sure if there's a specific limit.
CE
Cecilia
1 year ago
Ah, I remember learning about this in class. The general rule is to use embedded collections when the "many" side isn't too big. Separate collections are better for larger data sets.
BE
Ben
1 year ago
Ah, I see. So it's all about balancing performance and flexibility. Embedded collections are more efficient, but separate collections give you more control. Gotta weigh the options.
HE
Herminia
1 year ago
Hmm, I'm a bit unsure about this. I know embedded collections can be more efficient, but when should we really use them over separate collections?
FA
Fairy
1 year ago
This is a tricky one. I'll need to think carefully about the trade-offs between embedded collections and separate collections.
RO
Roxane
1 year ago
Okay, I think I've got this. The key is considering the size of the "many" side of the relationship. If it's not very large, embedded collections are probably the way to go.
VI
Viola
1 year ago
Hmm, this looks like a tricky one. I'll need to carefully read through the options and think about which solutions Huawei Cloud might provide.
MA
Margo
1 year ago
I’m not entirely confident, but doesn’t it have to do with ensuring reliability in financial reporting?
CL
Cletus
1 year ago
Hmm, this is a tricky one. I'm not entirely sure where to start, but I think I'll begin by verifying the tunnel protection is applied correctly. That could be the root cause of the "MM_NO_STATE" error.
BR
Brittni
1 year ago
I'm just imagining a database with a 'many' field the size of the Library of Congress. Talk about a document weight-lifting challenge!
JA
Janey
1 year ago
A) When the many is not very large
TA
Tammara
1 year ago
B) When the many is very large
LU
Luisa
1 year ago
A) When the many is not very large
CA
Carlee
1 year ago
C) Always
AL
Alesia
1 year ago
B) When the many is very large
RE
Reiko
1 year ago
A) When the many is not very large
LI
Lisha
1 year ago
D is the only sensible answer here. Embedded collections are great, but you have to use them judiciously.
MA
Marti
1 year ago
D) Never
HI
Hildred
1 year ago
B) When the many is very large
JU
Julieta
1 year ago
A) When the many is not very large
PA
Pamella
1 year ago
C? Really? Embedding collections should be the exception, not the rule. What are they thinking?
CA
Casie
1 year ago
Embedding collections should be the exception, not the rule.
AN
Annamae
1 year ago
C) Always
SH
Sharmaine
1 year ago
B) When the many is very large
TO
Tommy
1 year ago
A) When the many is not very large
LA
Lashaunda
2 years ago
But what if the many is very large? Wouldn't it be better to use a separate collection then?
MA
Marya
2 years ago
Definitely B. If the many is very large, embedding it just sounds like a recipe for a bloated document. Separate collections are the way to go.
LA
Lashonda
1 year ago
Embedding can work well for smaller amounts of data.
LE
Lelia
1 year ago
I always prefer separate collections for scalability.
DA
Dalene
1 year ago
I think it depends on the specific use case and data size.
KI
Kiera
1 year ago
I agree, separate collections are better for large amounts of data.
DO
Donette
2 years ago
I agree with Eladia. It would be more efficient to embed the collection in that case.
FR
Franchesca
2 years ago
I think when the many is not very large, an embedded collection makes the most sense. It keeps the data nicely organized and easy to access.
EL
Eladia
2 years ago
I think we should consider representing a one-to-many relationship in an embedded collection when the many is not very large.