A. Enforce the reference architecture.

B. Avoid error codes.

C. Reveal the nature of each Module.

D. Normalize patterns.

A. Do not use Entity Bulk Operation to ensure small lightweight updates

B. Only synchronize relevant data

C. Ensure sync granularity: Prepare for constant retries without repeating work due to network loss. Sync in chunks, incremental by entity

D. Only synchronize delta : Use control timestamps
C Avoid long synchronization in a single transaction

E. Sync only when strictly required
E Don't sync on every screen or online event

F. 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

A. Reusable UI Patterns for layout and display only - no Business logic.

B. have several integration services with different systems, performing the same type of O operation (e.g. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).

C. Theme, look & feel elements, menu, etc.

D. Generic Library module

E. Reusable Core Services with public entities, actions, and blocks.

F. Technical wrapper to consume and normalize an external service

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 exposed as read-only and API is available to centralize business logic for entity creation/update

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

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

F. 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.

G. 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

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

A. Generic Library module.

B. Reusable UI Patterns for layout and display only - no Business logic.

C. to have several integration services with different systems, performing the same type of operation (e.g. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).

D. technical wrapper to consume and normalize an external service.

E. Theme, look & feel elements, menu, etc.

A. ... tries to fetch data from local cache entity, if not there, get single entry from the external v 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

B. 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

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

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. ... Entity is not in Outsystems but in an external ERP system. IS just makes remote call to p 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

G. 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

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

I. ... caches only summary data that is frequently lister, joined or searched. Full detail for a O 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)

J. ... 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.

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

B. 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

C. ... 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

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

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

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

A. SSL Pinning does not mean hardcoding the public key into the code.

B. All of the above are true

C. Works on the client side and adds verification of the server certificate against hashes of public keys, which are pre-bundled with the mobile app

D. SSL Pinning or HTTP Public Key Pinning (HPKP) helps reduce man-in-the-middle attacks

A. Promotes segregation and loose coupling of services

B. Optimizes lifecycle independence

C. Minimizes impact of changes

D. Promotes abstraction of reusable services