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

Home
Popular vendors
- - Salesforce
  - Microsoft
  - Nutanix
  - Amazon
  - Google
  - CompTIA
  - SAP
  - VMware
  - Oracle
  - Fortinet
  - PeopleCert
  - Eccouncil
  - HP
  - Palo Alto Networks
  - Adobe
  - ServiceNow
  - Dell EMC
  - CheckPoint
  - Linux Foundation
Discount Deals New
About
Contact
Login
Sign up

Home
Discussions
OutSystems Discussions
Exam Architecture-Specialist-11 Topic 1 Question 8 Discussion

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

Actual exam question for OutSystems's Architecture-Specialist-11 exam

Question #: 8
Topic #: 1

[All Architecture-Specialist-11 Questions]

Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation

A... 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)

B... is a pattern with two modules, a connector module that can be used to encapsulate an external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.

CSame as Base ECS pattern, but have a local replica. Store data to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration API. Con: Less impact on source system

D... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

E... tries to fetch data from local cache entity, if not there, get single entry from the external system. Cache only that record (read-through caching) Use when whole database too big or costly to synchronize. Integration only touches a small portion of the database. Avoid if access to lists of data is needed up front

FSame as ECS with local replica but API module is provided. So any changes to the external system can notify OS, which OS then gets update from the ERP system (subscription system)

GSame 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

H... Entity is not in Outsystems but in an external ERP system. IS just makes remote call to external system/database. No data is being kept inside OS. Data retrieval may not be optimized as it needs to traverse two different systems to get the information back. Con: Integration API must support all use cases

I... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

J... a wrapper used to contain the logic, actions and data that will expose code that is inside of i external library or to inspect external database and import the data structures so they can be used as entities inside of OS

Show Suggested Answer Hide Answer

Suggested Answer: E

by Samira at Dec 24, 2023, 09:30 AM

Limited Time Offer

25%

Off

Get Premium Architecture-Specialist-11 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Chandra

11 months ago

Ooh, good point! I didn't notice the 'Core Module Pattern' part before. G) does seem to be a closer match, with the mention of the local replica and the separation of the synchronization logic. E) is more of a standalone caching pattern, while G) feels more like a variation on the core ECS pattern.

upvoted 0 times

...