OutSystems Exam Architecture-Specialist-11 Topic 5 Question 28 Discussion

Actual exam question for OutSystems's Architecture-Specialist-11 exam

Question #: 28
Topic #: 5

[All Architecture-Specialist-11 Questions]

What is NOT a best practice for Mobile Application Architecture: transactions & granularity?

AHave long synchronizations in a single transaction. Better UX as app does not need to sync all the time. Is prepared for constant offline or device standby

BEnsure order and sync granularity. Sync incrementally by entity with partial commit. This way O synchronizations is prepared for constant interruptions and allow retries without repeating the entire synchronization from the start.

Show Suggested Answer

Suggested Answer: A

by Gilma at Sep 17, 2024, 05:17 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Margot

2 months ago

Option B is the way to go, no doubt about it. Partial commits and retries? Sign me up! Though I do wonder if the developers had to sync their watches to get the timing right.

upvoted 0 times

Murray

1 months ago

User 3: Syncing watches for timing? That's an interesting thought, but I think they probably have other ways to handle that.

upvoted 0 times

...

Arletta

1 months ago

User 2: I agree, it's important to have that order and sync granularity for a smooth experience.

upvoted 0 times

...

Louisa

2 months ago

Option B is definitely the best choice. Partial commits and retries are key.

upvoted 0 times

...

Belen

2 months ago

Option A sounds like a recipe for disaster. Who wants an app that constantly syncs and drains the battery? Not me, that's for sure!

upvoted 0 times

...

Chauncey

3 months ago

I agree with Suzi. Option B is the clear winner here. Maintaining order and granularity is crucial for a robust mobile app architecture.

upvoted 0 times

Kaycee

1 months ago

Incremental sync by entity with partial commit is definitely the way to go.

upvoted 0 times

...

Thersa

1 months ago

Having long synchronizations in a single transaction can lead to issues.

upvoted 0 times

...

Abel

1 months ago

I agree with Suzi. Option B is the clear winner here.

upvoted 0 times

...

Glory

3 months ago

I believe ensuring order and sync granularity is key for mobile application architecture.

upvoted 0 times

...

Suzi

3 months ago

Option A is definitely not the best practice. Long synchronizations and offline scenarios do not mix well. Partial commits and incremental syncing are the way to go.

upvoted 0 times