New Year Sale ! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

OutSystems Exam Architecture-Specialist-11 Topic 2 Question 30 Discussion

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

Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Gregoria
2 months ago
Option B is the way to go, folks. It's like a 'Cliff's Notes' version of the external system - just the highlights, without all the fluff.
upvoted 0 times
...
Twanna
2 months ago
Option H is just too weird. 'A wrapper used to contain the logic, actions and data that will expose code that is inside of external library'? What does that even mean?
upvoted 0 times
Sanda
2 months ago
I think option H is trying to abstract away the complexity of interacting with external libraries or databases.
upvoted 0 times
...
Thad
2 months ago
Yeah, I agree. Option H seems like it's trying to do too many things at once.
upvoted 0 times
...
Ezekiel
2 months ago
I know, option H does sound confusing. It's like a wrapper for a wrapper.
upvoted 0 times
...
...
Elena
2 months ago
Option J is a bit too generic. It's talking about a connector and wrapper module, but doesn't really address the specific ECS summary cache pattern.
upvoted 0 times
...
Terina
3 months ago
Option I looks interesting, but it doesn't seem to fit the 'ECS Summary Cache only' requirement. It's more about just making remote calls without any local caching.
upvoted 0 times
Enola
2 months ago
We should look for an option that includes local caching for the ECS Summary Cache pattern.
upvoted 0 times
...
Ruth
2 months ago
Yeah, option I seems to focus more on remote calls without local caching.
upvoted 0 times
...
Dalene
2 months ago
I think option I is not the right fit for the ECS Summary Cache only requirement.
upvoted 0 times
...
...
Val
3 months ago
I'm leaning towards Option G. It describes a read-through caching approach, which aligns with the 'ECS Summary Cache only' variation.
upvoted 0 times
Carlton
2 months ago
Yes, it would help optimize data retrieval and avoid syncing the entire database.
upvoted 0 times
...
Oren
2 months ago
I agree, read-through caching would be beneficial for this pattern.
upvoted 0 times
...
Franklyn
3 months ago
Option G seems like a good fit for the ECS Summary Cache only variation.
upvoted 0 times
...
...
Diego
3 months ago
I'm leaning towards answer C. Separating synchronization logic could provide more flexibility in the long run.
upvoted 0 times
...
Wai
3 months ago
I disagree, I believe the answer is G. Fetching data from local cache first can be more efficient.
upvoted 0 times
...
Lizette
3 months ago
Option B seems to be the best match. It specifically mentions caching only the summary data and fetching the full details from the external system when needed.
upvoted 0 times
Solange
2 months ago
Yes, option B is the most suitable for the Core Module Pattern - ECS Summary Cache only variation.
upvoted 0 times
...
Wynell
2 months ago
Option B seems like a good choice, it focuses on caching summary data and fetching details when necessary.
upvoted 0 times
...
Annamae
3 months ago
I agree, option B mentions caching only summary data and fetching full details when needed.
upvoted 0 times
...
Narcisa
3 months ago
I think option B is the best match for Core Module Pattern - ECS Summary Cache only variation.
upvoted 0 times
...
Ressie
3 months ago
I agree, Option B mentions caching only summary data and fetching full details when needed from the external system.
upvoted 0 times
...
Malcolm
3 months ago
I think Option B is the best match for Core Module Pattern - ECS Summary Cache only variation.
upvoted 0 times
...
...
Erinn
3 months ago
I think the answer is A. Having a local replica for caching seems like a good idea.
upvoted 0 times
...

Save Cancel