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

OutSystems Architecture-Specialist-11 Exam - Topic 4 Question 56 Discussion

Which of the below is NOT a suitable advice for designing a Parallel mobile local storage?
A) Allow table dependency : Normalize tables to promote parallel data fetch
B) Use Fetch Data : Avoid cascading aggregates in Onlnitialize and OnReady
C) Avoid generic tables : Contains too much data, not all are relevant

OutSystems Architecture-Specialist-11 Exam - Topic 4 Question 56 Discussion

Actual exam question for OutSystems's Architecture-Specialist-11 exam
Question #: 56
Topic #: 4
[All Architecture-Specialist-11 Questions]

Which of the below is NOT a suitable advice for designing a Parallel mobile local storage?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Ilene at Jun 01, 2026, 05:27 AM

Limited Time Offer

25%

Off

Get Premium Architecture-Specialist-11 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Iluminada
16 hours ago
But B also makes sense. Cascading aggregates can slow down the process.
upvoted 0 times
...
Luisa
6 days ago
I agree with C. It can lead to performance issues.
upvoted 0 times
...
Earnestine
11 days ago
I feel C is the best choice. Generic tables complicate things.
upvoted 0 times
...
Carlene
16 days ago
C is definitely not suitable advice. Too much irrelevant data is a problem.
upvoted 0 times
...
Henriette
21 days ago
I disagree, A seems fine. What about C?
upvoted 0 times
...
Roy
26 days ago
I think option A is the right answer. Normalizing tables is essential.
upvoted 0 times
...
Colby
1 month ago
Not sure about A, isn't normalization sometimes overrated?
upvoted 0 times
...
Alysa
1 month ago
B is crucial, can't have those aggregates slowing things down.
upvoted 0 times
...
Audry
1 month ago
Wait, are we really avoiding cascading aggregates? Seems risky!
upvoted 0 times
...
Sunshine
2 months ago
I think C makes sense, generic tables can be a mess.
upvoted 0 times
...
Harrison
2 months ago
A is definitely the way to go for parallel fetching.
upvoted 0 times
...
Sarina
2 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.
upvoted 0 times
...
Bulah
2 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.
upvoted 0 times
...
Pauline
2 months ago
I remember practicing a question about avoiding cascading aggregates, so I feel like option B could be the right answer here.
upvoted 0 times
...
Vallie
2 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.
upvoted 0 times
...

Save Cancel