Halloween Special 2026! Get Up to 25% OFF Practice Questions! Limited Time - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

OutSystems Architecture-Specialist-11 Exam - Topic 1 Question 3 Discussion

Posted by Sherita on Nov 23, 2023 at 09:34 PM

Which of the below is NOT a Synchronization Best Practice for mobile application?

Suggested Answer: D

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
27 comments · newest first
AM
Amira 11 months ago
Not sure about syncing only relevant data... seems too limiting.
YE
Yen 11 months ago
Definitely agree with avoiding long syncs in one go.
HE
Heike 11 months ago
Wait, is using Entity Bulk Operation really a bad practice?
RU
Ruby 12 months ago
I think syncing on every screen is a bad idea.
MY
Myong 12 months ago
Sync only when required is a solid practice!
NO
Noemi 12 months ago
I recall that long syncs can be problematic, so C seems like a best practice. But I'm not sure about H; it sounds complicated.
SA
Sarah 1 year ago
I practiced a question like this, and I feel like F makes sense because we should only sync relevant data, but I'm not confident about the others.
BU
Buck 1 year ago
I'm not entirely sure, but I remember something about avoiding bulk operations. Maybe G is the one that doesn't fit?
SH
Shaun 1 year ago
I think option D sounds a bit redundant since it says "sync only when strictly required," which seems similar to A.
TO
Tom 1 year ago
I'm a bit unsure about a couple of these options. I'll need to review my notes on mobile sync best practices to make sure I don't accidentally choose the right answer.
KA
Kassandra 1 year ago
This is right up my alley! I've worked on a lot of mobile apps, so I'm familiar with the common synchronization pitfalls. I'm feeling pretty confident about this one.
HA
Halina 1 year ago
Okay, I think I've got a handle on this. The key is to identify the practice that goes against the principles of efficient, incremental, and reliable synchronization. I'll give it my best shot.
AN
Angelo 1 year ago
This looks like a tricky question. I'll need to carefully read through the options and think about which one is the least optimal synchronization practice.
DE
Derick 1 year ago
Hmm, I'm a bit confused by some of these options. I'll need to make sure I understand the best practices for mobile app synchronization before I can confidently choose the wrong one.
CA
Carmela 1 year ago
Fear of failure is definitely the biggest obstacle when it comes to trying new things. That's the answer that makes the most sense to me.
LE
Leonor 1 year ago
Hmm, this is a tricky one. I'm not entirely sure which risk response strategy this scenario is referring to. I'll need to re-read the question and think it through step-by-step.
LE
Leontine 3 years ago
Haha, I love how this question is really making us think! I'm going to go with B - 'Only synchronize delta: Use control timestamps'. That's a classic mobile sync technique that helps reduce data transfer. Though I can see the merits of the other options as well.
FA
Fannie 3 years ago
Hmm, I'm leaning more towards D - 'Sync only when strictly required'. That aligns with the general principle of minimizing data transfer in mobile apps. Though H also makes a lot of sense, so I'm torn between those two options.
GL
Glenn 3 years ago
I'm not convinced G is the right answer. I think the best answer is H - 'Ensure sync granularity: Prepare for constant retries without repeating work due to network loss. Sync in chunks, incremental by entity'. That really captures the essence of good synchronization practices for mobile.
GL
Gladys 3 years ago
↳ replying to Glenn
Yes, H is definitely an important practice to follow. It helps in handling network issues effectively.
TE
Tequila 3 years ago
↳ replying to Glenn
H) Ensure sync granularity: Prepare for constant retries without repeating work due to network loss. Sync in chunks, incremental by entity
LA
Launa 3 years ago
↳ replying to Glenn
I agree with F. Syncing only relevant data is crucial for efficient synchronization.
EM
Emerson 3 years ago
↳ replying to Glenn
F) Only synchronize relevant data
AN
An 3 years ago
↳ replying to Glenn
I prefer A as well. It's important to sync only when necessary to avoid unnecessary data usage.
NO
Norah 3 years ago
↳ replying to Glenn
E) Don't sync on every screen or online event
OL
Olive 3 years ago
↳ replying to Glenn
A) Sync only when required.
JA
Janey 3 years ago
This is a great question that really tests our understanding of mobile app synchronization best practices. I'm pretty sure the answer is G - 'Do not use Entity Bulk Operation to ensure small lightweight updates'. Bulk operations can lead to large data transfers, which is not ideal for mobile apps.
0/2000 characters

Save Cancel