MENU
What is NOT a best practice for Mobile Application Architecture: Local Storage?
Suggested Answer: B
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
32 comments · newest first
BR
Brandon
11 months ago
Definitely not B, that would kill performance!
LA
Lanie
11 months ago
Wait, is syncing at process start really the best way?
TO
Tonette
11 months ago
I thought syncing on every event was standard?
JE
Jettie
12 months ago
Totally agree, option B is a bad practice!
JA
Jacquelyne
12 months ago
Sync on every screen? That's a no-go.
MU
Muriel
12 months ago
I vaguely remember something about avoiding excessive syncing, so B might be the right answer, but I need to double-check my notes.
PA
Pansy
1 year ago
I feel like C makes sense for optimizing data usage, but I can't recall if it was explicitly mentioned as a best practice.
DE
Detra
1 year ago
I remember practicing a question about sync frequency, and I think A is definitely a best practice.
LI
Lindsey
1 year ago
I think option B sounds wrong because syncing on every screen could lead to performance issues, but I'm not completely sure.
AL
Alise
1 year ago
I'm confident that B is the correct answer. Syncing on every screen or online event is not efficient and would drain the user's battery and data plan unnecessarily.
BE
Bettina
1 year ago
The key here is to sync data efficiently based on the use case, as option C suggests. Syncing everything on every screen would be overkill and impact performance.
EU
Eun
1 year ago
Hmm, I'm a bit unsure about this one. I'll need to think through the different options carefully to make sure I understand the best practices for local storage in mobile apps.
TH
Thaddeus
1 year ago
This question seems straightforward. I think the answer is B - syncing on every screen or online event is not a best practice for mobile app local storage.
GR
Gregg
1 year ago
Okay, let me see... I know there are some installation steps, but I'm not sure about the exact order or requirements. I'll have to review my notes.
LE
Leonora
2 years ago
Ah, the old 'sync at process start and online' trick. Classic mobile app architecture right there. Can't go wrong with that one.
GU
Gussie
2 years 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!
ME
Merilyn
2 years ago
Fannie: Exactly, it would just slow down the app and waste resources.
FA
Fannie
2 years ago
User 2: Yeah, it would be way too much unnecessary data transfer.
LI
Linwood
2 years ago
User 1: I agree, syncing on every screen or event is definitely not a best practice.
CA
Carole
2 years 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?
LA
Lacresha
2 years ago
Adopting the correct sync frequency is key to a well-structured Mobile Application Architecture.
TO
Tonette
2 years ago
Syncing on every screen or online event would definitely be inefficient.
JA
Jacquelyne
2 years ago
I agree, it's important to only sync the necessary data to avoid wasting resources.
RE
Reita
2 years ago
Exactly! Syncing only the data required for each use case helps optimize performance.
LA
Lavonne
2 years ago
Syncing on every screen or online event? That's just asking for trouble. Way too much data being transferred for no good reason.
NI
Nida
2 years ago
Syncing on every screen or online event? That's just asking for trouble. Way too much data being transferred for no good reason.
TH
Thurman
2 years 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
MO
Mozelle
2 years ago
B) Sync on every screen or online event
VE
Vesta
2 years ago
A) Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online
AR
Arlyne
2 years ago
Hmm, that makes sense. It's important to only sync the data needed for each specific use case.
DE
Delmy
2 years ago
Actually, I believe the best practice is to sync data required per use case.
AR
Arlyne
2 years ago
I think the best practice is to sync on every screen or online event.