OutSystems Architecture Specialist (OutSystems 11) Exam Architecture-Specialist-11 Exam Dumps: Updated Questions & Answers (October 2025)

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

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

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

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

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

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

. 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

Portal

Intranet

Independent Apps

Architecture Validation

Architecture Canvas

Architecture Framework

AI Mentor

Security and scalability.

Speed up the development phase.

Improve performance and maintainability.

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

Screens

Static Entities

Server Actions

Database Entities

Service Actions

Local Storage Entities

Structures

It optimizes lifecycle independence.

It identifies possible performance bottlenecks.

It minimizes the impact of changes.

It promotes a correct abstraction of reusable services.

All public entities in Core Modules should be set to Read-only

No business logic in the Foundational Modules

No core entities in Foundational Modules

No screens in the End User Layer

No front-end screens in Core Modules

When minor customizations to the base theme should be done inside the app theme.

It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.

When you want to introduce extensive changes to an existing theme.

When it is not possible to benefit from any existing theme and extensive changes are needed.

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

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)

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

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

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

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

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

Concepts are disclosed to the Architecture team

Concepts are assembled into Modules

Concepts are added to the layers of the Architecture Canvas