OutSystems Architecture-Specialist-11 Exam - 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?

AAdopt the correct sync frequency: Either at process start and online or at process/transaction end and online

BSync on every screen or online event

CSync data required per use case: Sync summary data on Session start. On data selection, sync p 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, a

Show Suggested 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

Brandon

3 months ago

Definitely not B, that would kill performance!

upvoted 0 times

...

Lanie

4 months ago

Wait, is syncing at process start really the best way?

upvoted 0 times

...

Tonette

4 months ago

I thought syncing on every event was standard?

upvoted 0 times

...

Jettie

4 months ago

Totally agree, option B is a bad practice!

upvoted 0 times

...

Jacquelyne

4 months ago

Sync on every screen? That's a no-go.

upvoted 0 times

...

Muriel

4 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.

upvoted 0 times

...

Pansy

5 months 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.

upvoted 0 times

...

Detra

5 months ago

I remember practicing a question about sync frequency, and I think A is definitely a best practice.

upvoted 0 times

...

Lindsey

5 months ago

I think option B sounds wrong because syncing on every screen could lead to performance issues, but I'm not completely sure.

upvoted 0 times

...

Alise

5 months 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.

upvoted 0 times

...

Bettina

5 months 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.

upvoted 0 times

...

Eun

5 months 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.

upvoted 0 times

...

Thaddeus

5 months 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.

upvoted 0 times

...

Gregg

5 months 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.

upvoted 0 times

...

Leonora

1 year 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

1 year 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 year ago

Fannie: Exactly, it would just slow down the app and waste resources.

upvoted 0 times

...

Fannie

1 year ago

User 2: Yeah, it would be way too much unnecessary data transfer.

upvoted 0 times

...

Linwood

1 year ago

User 1: I agree, syncing on every screen or event is definitely not a best practice.

upvoted 0 times

...

Carole

1 year 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

1 year ago

Adopting the correct sync frequency is key to a well-structured Mobile Application Architecture.

upvoted 0 times

...

Tonette

1 year ago

Syncing on every screen or online event would definitely be inefficient.

upvoted 0 times

...

Jacquelyne

1 year ago

I agree, it's important to only sync the necessary data to avoid wasting resources.

upvoted 0 times

...

Reita

1 year ago

Exactly! Syncing only the data required for each use case helps optimize performance.

upvoted 0 times

...

Lavonne

1 year 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

1 year 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

1 year 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

...