OutSystems : Architecture-Specialist-11 Questions & Answers

Which of the below matches the most to Core Module Pattern - Core Entity Pattern...

• A. 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
• B. ... 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
• C. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
• D. 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)
• E. is a pattern with two modules, a connector module that can be used to encapsulate an O external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.
• F. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
• G. ... 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
• H. 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
• I. ... 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
• J. ... 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)

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

• A. Only synchronize relevant data
• B. Do not use Entity Bulk Operation to ensure small lightweight updates
• C. Only synchronize delta : Use control timestamps
  C Avoid long synchronization in a single transaction
• D. Sync only when required. p At session start: sync summary data to local storage At process start: sync process detail to local storage At process/transaction end, sync back to server
• E. Sync only when strictly required
  E Don't sync on every screen or online event
• F. Ensure sync granularity: Prepare for constant retries without repeating work due to network loss. Sync in chunks, incremental by entity

In which Architecture Canvas layer do you expect to have a higher reusability rate?

• A. Core layer
• B. Foundation layer
• C. End-User layer

Themes and Layouts are an important element of an application. In which of the following would you define these elements?

• A. MyApp_MTh, in the Foundation layer.
• B. MyApp_Th Module, in the End-User layer
• C. MyApp_BL, in the Foundation Layer.
• D. MyApp_CS Module, in the Foundation layer

Which of the following is NOT a benefit of having well-defined application architecture?

• A. Supports planning
• B. Poor service abstraction
• C. Reduces costs
• D. Reduces risk