MENU
Which of the below is NOT a suitable advice for designing a Parallel mobile local storage?
Suggested Answer: A
Get Premium Architecture-Specialist-11 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
15 comments · newest first
IL
Iluminada
2 months ago
But B also makes sense. Cascading aggregates can slow down the process.
LU
Luisa
2 months ago
I agree with C. It can lead to performance issues.
EA
Earnestine
2 months ago
I feel C is the best choice. Generic tables complicate things.
CA
Carlene
2 months ago
C is definitely not suitable advice. Too much irrelevant data is a problem.
HE
Henriette
2 months ago
I disagree, A seems fine. What about C?
RO
Roy
2 months ago
I think option A is the right answer. Normalizing tables is essential.
CO
Colby
3 months ago
Not sure about A, isn't normalization sometimes overrated?
AL
Alysa
3 months ago
B is crucial, can't have those aggregates slowing things down.
AU
Audry
3 months ago
Wait, are we really avoiding cascading aggregates? Seems risky!
SU
Sunshine
3 months ago
I think C makes sense, generic tables can be a mess.
HA
Harrison
3 months ago
A is definitely the way to go for parallel fetching.
SA
Sarina
3 months ago
I feel like I've seen a similar question before, and I think avoiding generic tables is usually recommended, so maybe option C is the one that's not suitable.
BU
Bulah
4 months ago
I have a vague recollection that generic tables can lead to performance issues, but I can't recall if that's directly related to parallel storage design.
PA
Pauline
4 months ago
I remember practicing a question about avoiding cascading aggregates, so I feel like option B could be the right answer here.
VA
Vallie
4 months ago
I think option A sounds familiar, but I'm not entirely sure if normalizing tables is always the best approach for parallel data fetch.