OAPI is different compared to API. What is inside an OAPI?

• A. REST API
• B. Service Action

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

• 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
• B. Same 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)
• C. ... 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)
• D. ... Entity is exposed as read-only and API is available to centralize business logic for entity ^ creation/update
• E. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
• F. ... tries to fetch data from local cache entity, if not there, get single entry from the external p 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.
• G. ... 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.
• H. Same 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
• I. ... 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
• J. ... a wrapper used to contain the logic, actions and data that will expose code that is inside of ) external library or to inspect external database and import the data structures so they can be used as entities inside of OS

What is NOT a best practice for Mobile Application Architecture: Local Storage?

• A. Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online
• B. Sync on every screen or online event
• C. Sync data required per use case: Sync summary data on Session start. On data selection, sync p its details.

Which of the below is NOT a suitable advice for designing a Parallel mobile local storage?

• A. Use Fetch Data : Avoid cascading aggregates in Onlnitialize and OnReady
• B. Avoid generic tables : Contains too much data, not all are relevant
• C. Allow table dependency : Normalize tables to promote parallel data fetch