Pass the OutSystems Architecture Specialization Architecture-Specialist-11 Questions and answers with CertsForce

Transparency Service Pattern 1 way (simplification)

Library : Extension Pattern

ECS with isolated synchronization logic

ECS Lazy Load variation

ECS with publish/subscribe through an ESB

ECS Summary cache only variation

Library : Connector Pattern

MyApp_CS Module, in the Foundation layer

MyApp_BL, in the Foundation Layer.

MyApp_Th Module, in the End-User layer

MyApp_MTh, in the Foundation layer.

Organize

Plan

Assemble

Disclose

The "specialize a built-in Style Guide" scenario should be used when the changes to the base theme are not extensive.

The "clone a built-in Style Guide" should be used when you want to extend an existing theme.

Build-your-own Style Guide should be used when the changes in the theme are not extensive.

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

Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.

A BL becomes a Calculation Engine if it performs complex calculations, (e.g. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.

Logic to Synchronize data in CS's with an external system. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.

Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.

Logic to Synchronize data in CS's with an external system. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.

A BL becomes a Calculation Engine if it performs complex calculations, (e.g. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.

Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.

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

Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.

Patterns - are blocks that provide common and reusable UI. Chat message, date picker and carousel are a few examples. Contains reusable UI components.

All of the above are true

Theme - for the look and feel of your applications, which includes screen layouts, global stylesheet and grid definitions. Contains CSS styles and classes.

Templates - Defines the structure of the application modules. Templates contains screen p definitions and basic set of functionalities, including authentication.

Contains common layouts, menu, login and reference to the theme .

Poor service abstraction

Unmanageable dependencies

Manages complexity

Slow-moving legacy systems

End-User, Core, and Foundation Modules.

Foundation and Core Modules

Only Foundation Modules.

End-User and Core Modules.

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

Technical wrapper to consume and normalize an external service

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

Theme, look & feel elements, menu, etc.

Generic Library module

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