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

Inflexible and slow-moving legacy systems : adapting legacy systems to business changes may be difficult. Changes in complex and inflexible systems can take a long time

Tech Debt : AI Mentor will raise architectural tech debt such as cyclic dependency and side to side dependency

Unmanageable dependencies : System not isolated from each other. Updating or replacing a system has a cascade/snowball effect on other systems

Poor service abstraction : Business concepts not correctly isolated, business rules tend to be spread over different systems and little to no code reuse

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

Limit Server side calls to online transactions or Synchronization. Do the bulk of the operations on the Client Side before passing information to the Server Side.

Synchronize on every screen or online event for better granularity

No direct calls to backend systems. Do call to Outsystems Core Services and Outsystems will handle the interaction with external backend systems.

Direct calls is bad from Security, Performance and Maintainability standpoint. Direct calls will require javascript Code and javascript Code is harder to maintain.

Allow table dependency : Normalize tables to promote parallel data fetch

Use Fetch Data : Avoid cascading aggregates in Onlnitialize and OnReady

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

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

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

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

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

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

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

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

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

Discovery only validates architecture rules at the module level.

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

Discovery cannot categorise modules to domains

End-User layer

Core layer

Foundation layer

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

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

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

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

Screens

Static Entities

Server Actions

Database Entities

Service Actions

Local Storage Entities

Structures