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 Exam Architecture-Specialist-11 Topic 1 Question 16 Discussion

Actual exam question for OutSystems's Architecture-Specialist-11 exam
Question #: 16
Topic #: 1
[All Architecture-Specialist-11 Questions]

Which of the below matches the most to Core Module Pattern - ECS with Isolated Synchronization Logic Pattern...

Show Suggested Answer Hide Answer
Suggested Answer: B

by Janae at May 12, 2024, 03:55 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
Eleonora
26 days ago
Wait, there's an 'ECS with Isolated Synchronization Logic Pattern'? Sounds like the engineers had a field day coming up with that one. I bet they're real fun at parties.
upvoted 0 times
Kizzy
3 days ago
I think option E matches the most to the Core Module Pattern - ECS with Isolated Synchronization Logic Pattern.
upvoted 0 times
...
...
Aleisha
1 months ago
I'm leaning towards option G - the 'read-through caching' approach. Seems like a smart way to handle a large database without having to sync the whole thing. And only fetching individual records as needed is efficient.
upvoted 0 times
...
King
1 months ago
Haha, 'ERP system' and 'external system/database' - I feel like that's half the questions on these exams these days. Gotta love all the enterprise integrations we have to deal with.
upvoted 0 times
Leah
18 days ago
E) ... caches only summary data that is frequently lister, joined or searched. Full detail for a single entry is fetched directly from external system. Use when whole database too big or costly to synchronize. Details are only required for single entities (not lists)
upvoted 0 times
...
Denise
1 months ago
A) Same as ECS with local replica but synchronization logic is separated. Pro: Code independence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS
upvoted 0 times
...
...
Cary
2 months ago
Option H looks interesting too. A 'connector module' to encapsulate the external API, and a 'wrapper module' to expose the normalized API - that seems to fit the pattern description pretty well.
upvoted 0 times
Cyndy
19 days ago
Yes, Option H seems like a good choice for Core Module Pattern - ECS with Isolated Synchronization Logic Pattern. It helps in encapsulating the external API and providing a normalized API to consumers.
upvoted 0 times
...
Maryann
1 months ago
Option H looks interesting too. A 'connector module' to encapsulate the external API, and a 'wrapper module' to expose the normalized API - that seems to fit the pattern description pretty well.
upvoted 0 times
...
...
Xenia
2 months ago
The Core Module Pattern - ECS with Isolated Synchronization Logic Pattern sounds a lot like option A. It mentions separating the synchronization logic, which aligns with the 'Sync can orchestrate several CS' part of the description. Definitely worth a closer look.
upvoted 0 times
...
Bobbye
2 months ago
I prefer option D because it leverages entity use and has a local cache for simpler integration.
upvoted 0 times
...
Maybelle
2 months ago
I agree with Blythe. Option A provides code independence and separates synchronization logic.
upvoted 0 times
...
Blythe
2 months ago
I think option A matches the most to Core Module Pattern - ECS with Isolated Synchronization Logic Pattern.
upvoted 0 times
...
Bettyann
2 months ago
I see your point, Nakisha. But I personally think option G is the most suitable as it fetches data from local cache entity first.
upvoted 0 times
...
Nakisha
2 months ago
I disagree, I believe option D is the best match because it leverages entity use and has a simpler integration API.
upvoted 0 times
...
Shannan
2 months ago
I think option A matches the most to Core Module Pattern - ECS with Isolated Synchronization Logic Pattern.
upvoted 0 times
...

Save Cancel