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

Ryan

3 months ago

I thought long transactions were okay for UX? Confused here.

upvoted 0 times

...

Yolande

4 months ago

B makes more sense for handling interruptions.

upvoted 0 times

...

Lang

4 months ago

Wait, are we really suggesting long transactions? That seems off.

upvoted 0 times

...

Chantay

4 months ago

Totally agree with B! Incremental sync is the way to go.

upvoted 0 times

...

Art

4 months ago

A long sync in one transaction sounds risky.

upvoted 0 times

...

Rodrigo

4 months ago

I definitely remember that partial commits are better for handling interruptions. It seems like option B aligns more with best practices we studied.

upvoted 0 times

...

Marleen

5 months ago

I feel like option A might be a trap. Long transactions could lead to issues if the app goes offline, but I can't recall the exact details.

upvoted 0 times

...

Jesusa

5 months ago

I think we practiced a question about synchronization granularity, and it emphasized the need for incremental syncs. That makes sense, right?

upvoted 0 times

...

Jesusita

5 months ago

I remember discussing the importance of keeping transactions short to improve user experience, but I'm not sure if long synchronizations are really the best approach.

upvoted 0 times

...

Chuck

5 months ago

I'm pretty confident on this one. The correct answer is option B - ensuring order and sync granularity. Syncing incrementally by entity with partial commit is the best way to handle interruptions and allow retries without repeating the entire sync.

upvoted 0 times

...

Stefany

5 months ago

I'm a bit confused on this one. Is having long synchronizations in a single transaction really a bad practice? Wouldn't that give a better user experience since the app doesn't need to sync all the time? I'll have to re-read the options carefully.

upvoted 0 times

...

Raymon

5 months ago

Okay, I think I know the answer here. The best practice is to have small, granular transactions that can be synced incrementally. That way, if there's an interruption, you can just retry the partial sync without having to start over.

upvoted 0 times

...

Deeanna

5 months ago

Hmm, this one seems tricky. I'll need to think carefully about the best practices for mobile app architecture and transactions. I don't want to get caught with a long synchronization that could fail due to interruptions.

upvoted 0 times

...

Lindsey

5 months ago

This seems like a straightforward question about controlling the visibility of a Visualforce component. I think the key is understanding how the rendered attribute works.

upvoted 0 times

...

Margot

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

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

upvoted 0 times

...

Louisa

1 year ago

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

upvoted 0 times

...

Belen

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

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

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

upvoted 0 times

...

Thersa

1 year ago

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

upvoted 0 times

...

Abel

1 year ago

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

upvoted 0 times

...

Glory

1 year ago

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

upvoted 0 times

...

Suzi

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