New Year Sale ! 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 Exam Architecture-Specialist-11 Topic 1 Question 27 Discussion

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

What is NOT a best practice for Mobile Application Architecture: Local Storage?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Jade at Sep 18, 2024, 10:41 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Leonora
2 months ago
Ah, the old 'sync at process start and online' trick. Classic mobile app architecture right there. Can't go wrong with that one.
upvoted 0 times
...
Gussie
3 months ago
Seriously, who would even consider syncing on every screen or event? That's like trying to fill a swimming pool with a teaspoon. Absurd!
upvoted 0 times
Merilyn
1 months ago
Fannie: Exactly, it would just slow down the app and waste resources.
upvoted 0 times
...
Fannie
1 months ago
User 2: Yeah, it would be way too much unnecessary data transfer.
upvoted 0 times
...
Linwood
1 months ago
User 1: I agree, syncing on every screen or event is definitely not a best practice.
upvoted 0 times
...
...
Carole
3 months ago
Hah! Sync data required per use case? Sounds like common sense to me. Why waste time and bandwidth syncing stuff you don't need?
upvoted 0 times
Lacresha
2 months ago
Adopting the correct sync frequency is key to a well-structured Mobile Application Architecture.
upvoted 0 times
...
Tonette
2 months ago
Syncing on every screen or online event would definitely be inefficient.
upvoted 0 times
...
Jacquelyne
2 months ago
I agree, it's important to only sync the necessary data to avoid wasting resources.
upvoted 0 times
...
Reita
2 months ago
Exactly! Syncing only the data required for each use case helps optimize performance.
upvoted 0 times
...
...
Lavonne
3 months ago
Syncing on every screen or online event? That's just asking for trouble. Way too much data being transferred for no good reason.
upvoted 0 times
Nida
2 months ago
Syncing on every screen or online event? That's just asking for trouble. Way too much data being transferred for no good reason.
upvoted 0 times
...
Thurman
2 months ago
C) Sync data required per use case: Sync summary data on Session start. On data selection, sync its details. Example: if you are accessing Purchasing data, sync the summary data on Session start. On selecting the Purchasing item, sync the details of the Purchasing item such as photos or price
upvoted 0 times
...
Mozelle
3 months ago
B) Sync on every screen or online event
upvoted 0 times
...
Vesta
3 months ago
A) Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online
upvoted 0 times
...
...
Arlyne
3 months ago
Hmm, that makes sense. It's important to only sync the data needed for each specific use case.
upvoted 0 times
...
Delmy
3 months ago
Actually, I believe the best practice is to sync data required per use case.
upvoted 0 times
...
Arlyne
3 months ago
I think the best practice is to sync on every screen or online event.
upvoted 0 times
...

Save Cancel