최신OutSystems Architecture Specialist (OutSystems 11) - Architecture-Specialist-11무료샘플문제

A. Is the end result of Architecture Design Process. At this point you should add dependencies between the Modules.

B. Above is the answer

A. Architecture Canvas

B. Architecture Framework

C. AI Mentor

D. Architecture Validation

A. ECS Lazy Load variation

B. Library : Extension Pattern

C. ECS with direct integration

D. ECS with publish/subscribe through an ESB

E. Transparency Service Pattern

F. Base ECS pattern

G. ECS Summary cache only variation

H. Library : Connector Pattern

I. ECS with isolated synchronization logic

J. Transparency Service Pattern 1 way (simplification)

A. Have long synchronizations in a single transaction. Better UX as app does not need to sync all the time. Is prepared for constant offline or device standby

B. Ensure order and sync granularity. Sync incrementally by entity with partial commit. This way O synchronizations is prepared for constant interruptions and allow retries without repeating the entire synchronization from the start.

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

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

C. Technical wrapper to consume and normalize an external service

D. Generic Library module

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

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

A. Layer Applications Correctly

B. Layer Modules Correctly

C. Don't Mix Owners

D. Layer Entities Correctly

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

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

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

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

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

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

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

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

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. Join all integrations into a single Module.

B. Keep concepts with different lifecycles apart.

C. Isolate all business concepts.

D. Disclose business concepts and integration needs.

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

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

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. Generic Library module.

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