OutSystems Architecture Specialist (OutSystems 11) - Architecture-Specialist-11무료 덤프문제 풀어보기

A. Process to package modules into apps

B. Answer is the above.

A. Efficiency : Efficiency which relates to the performance to the amount of resources used

B. Maintainability : Maintainability which relates to the effort needed to make modifications

C. Usability : Usability from the point of view of the users

D. Security : Security which relates to the strength of the of the software against cybersecurity attacks

E. Portability : Portability which defines the ability to move software between environments

F. Reliability : Reliability which ensures that a software solution can maintain it performance over a period of time

G. Functionality : Functionality as a set of functions that satisfy needs

A. Normalize patterns.

B. Enforce the reference architecture.

C. Avoid error codes.

D. Reveal the nature of each Module.

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 needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

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

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

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

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

A. Speed up the development phase.

B. Improve performance and maintainability.

C. Allows apps and the Style Guide to be deployed to Production.

D. Security and scalability.

A. Don't Mix Owners

B. Layer Entities Correctly

C. Don't Mix Sponsers : Split the Apps based on the Lines of Business

D. Layer Applications Correctly

E. Layer Modules Correctly

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

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 synchronization logic is separated. Pro: Code independence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS

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

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

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

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

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

A. Sync on every screen or online event

B. Sync data required per use case: Sync summary data on Session start. On data selection, sync p its details.

C. Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online

A. Owners of the Application should not be mixed, but mixing Sponsors has no direct impact on the release.

B. If you follow all the rules for validating modules, your application composition will be sound, and easy to maintain and deploy.

C. Applications in the Foundation layer can reference Applications in the End-user layer.

D. Common modules and services should be isolated in a separate app that can be referenced by other apps.