Deal of The Day! 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 Architecture-Specialist-11 Exam - Topic 5 Question 28 Discussion

What is NOT a best practice for Mobile Application Architecture: transactions & granularity?
A) Have 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
B) Ensure 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.

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?

Show Suggested Answer Hide 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:

0/2000 characters
Submit Cancel
Ryan
9 months ago
I thought long transactions were okay for UX? Confused here.
upvoted 0 times
...
Yolande
10 months ago
B makes more sense for handling interruptions.
upvoted 0 times
...
Lang
10 months ago
Wait, are we really suggesting long transactions? That seems off.
upvoted 0 times
...
Chantay
10 months ago
Totally agree with B! Incremental sync is the way to go.
upvoted 0 times
...
Art
10 months ago
A long sync in one transaction sounds risky.
upvoted 0 times
...
Rodrigo
10 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
11 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
11 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
11 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
11 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
11 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
11 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
11 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
11 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
2 years 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
2 years 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
2 years ago
User 2: I agree, it's important to have that order and sync granularity for a smooth experience.
upvoted 0 times
...
Louisa
2 years ago
Option B is definitely the best choice. Partial commits and retries are key.
upvoted 0 times
...
...
Belen
2 years 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
2 years 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
2 years ago
Incremental sync by entity with partial commit is definitely the way to go.
upvoted 0 times
...
Thersa
2 years ago
Having long synchronizations in a single transaction can lead to issues.
upvoted 0 times
...
Abel
2 years ago
I agree with Suzi. Option B is the clear winner here.
upvoted 0 times
...
...
Glory
2 years ago
I believe ensuring order and sync granularity is key for mobile application architecture.
upvoted 0 times
...
Suzi
2 years 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
Sharee
2 years ago
It's important to be prepared for constant interruptions in mobile app architecture.
upvoted 0 times
...
Temeka
2 years ago
Partial commits and incremental syncing are much more efficient.
upvoted 0 times
...
Ivory
2 years ago
Partial commits and incremental syncing are much more efficient.
upvoted 0 times
...
Jennie
2 years ago
I agree, long synchronizations can be a hassle.
upvoted 0 times
...
Ilene
2 years ago
I agree, long synchronizations can be a hassle.
upvoted 0 times
...
Yoko
2 years ago
Option A is definitely not the best practice.
upvoted 0 times
...
Elly
2 years ago
Option A is definitely not the best practice.
upvoted 0 times
...
...
Carey
2 years ago
I agree with Odette. It's better to sync incrementally by entity with partial commit for better UX.
upvoted 0 times
...
Odette
2 years ago
I think having long synchronizations in a single transaction is not a best practice.
upvoted 0 times
...

Save Cancel