OutSystems Architecture Specialist (OutSystems 11) Sample Questions:

1. What is NOT a best practice for Mobile Application Architecture: transactions & granularity?

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

2. Which of the following is an Assembling principle?

A) Disclose business concepts and integration needs.
B) Isolate all business concepts.
C) Join all integrations into a single Module.
D) Keep concepts with different lifecycles apart.

3. In which of the following scenarios should you choose to clone a built-in Style Guide?

A) It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.
B) When minor customizations to the base theme should be done inside the app theme.
C) When it is not possible to benefit from any existing theme and extensive changes are needed.
D) When you want to introduce extensive changes to an existing theme.

4. Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation

A) 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
B) ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
C) ... a wrapper used to contain the logic, actions and data that will expose code that is inside of i external library or to inspect external database and import the data structures so they can be used as entities inside of OS
D) ... 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.
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) ... 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
G) ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
H) ... 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)
I) 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)
J) 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

5. Which are NOT part of the major concepts that needs to be investigated in the Disclose phase in Architecture Design Process?

A) Information Architecture
B) User Experience Expectations
C) Integration Technology
D) Architecture Canvas Modules
E) User Stories, Personas and Roles

Solutions: