Architecture-Specialist-11 OutSystems Architecture Specialist (OutSystems 11) Exam Free Practice Exam Questions (2025 Updated)

Enforce the reference architecture.

Avoid error codes.

Normalize patterns.

Reveal the nature of each Module.

Assemble

Shape

Disclose

Organize

framework to support Architecture Conventions for Modules in Outsystems

framework to support application architecture design in Outsystems

framework to support Architecture Design Process in Outsystems

All of the above

Monitoring & Logging : for effective monitoring & logging, requires centralized service

Inter-process communication : network latency and hiccups

Complicated Debugging and troubleshooting : root cause may be deep inside the chain of services

Security : need to manage credentials and access management

Limited data mashup in memory and limited to APIs

Multiple transactions committed independently

No Downward References To Foundation Modules

No Side References Between End-User Modules

No Circular References

No Upward References

It's an automatic way to find and fix architecture issues.

It's a systematic approach to architecture design

It promotes the business users' collaboration and understanding

It's a faster architecture design

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

Non-core Entities

Entities to save UI states

Core Entities (exposed as read-only)

CRUD actions for Entities

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.

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

Above is the answer

Store password in local storage

Encrypt (only) sensitive data

Authentication : Use google or facebook for online authentication or fingerprint or pin for offline authentication

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.

Foundation

Ochestrator

End-User Layer

Core

Don't join concepts with different lifecycles

Apply known design patterns

N/A

Join conceptually-related concepts

Isolate reusable logic from Integration logic

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

Poor service abstraction

Reduces costs

Reduces risk

Supports planning

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 (•) 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)

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

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)

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

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

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

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

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