최신 Architecture-Specialist-11 무료덤프 - OutSystems Architecture Specialist (OutSystems 11)

A. MyApp_CS Module, in the Foundation layer

B. MyApp_BL, in the Foundation Layer.

C. MyApp_MTh, in the Foundation layer.

D. MyApp_Th Module, in the End-User layer

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

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

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

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

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

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 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. Use Fetch Data : Avoid cascading aggregates in Onlnitialize and OnReady

B. Allow table dependency : Normalize tables to promote parallel data fetch

C. Avoid generic tables : Contains too much data, not all are relevant

A. Core modules should not have Core Entities.

B. Core modules should have Front-end Screens for testing purposes.

C. Core modules should have public Read-only Entities.

D. Core modules should not have business logic.

A. Ensure it belongs to the correct layer

B. Enforce the reference architecture

C. Reveal nature of each module

D. Normalize known patterns

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

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

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

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

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

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

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

A. Minimizes impact of changes

B. Optimizes lifecycle independence

C. Promotes abstraction of reusable services

D. Promotes segregation and loose coupling of services

A. Discovery cannot categorise modules to domains

B. Discovery only validates architecture rules at the module level.

C. Discovery automatically assigns a module to an Architecture Canvas layer, following the module's naming convention.

D. Discovery allows you to determine for every module, which elements are being consumed by other modules.