OutSystems Architecture-Specialist-11 Exam Syllabus Topics:

OutSystems Architecture Specialist (OutSystems 11) Sample Questions:

Question #1
Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation

A. ... 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
B. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
C. ... 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
D. 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)
E. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
F. ... 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
G. ... 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.
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 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
J. 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

Question #2
Which of the below is not part of the Architecture Validation

A. No Circular References
B. No Upward References
C. No Side References Between End-User Modules
D. No Downward References To Foundation Modules

Question #3
Which of the following Data elements can we find in a End-User layer Module?

A. Non-core Entities
B. Entities to save UI states
C. Core Entities (exposed as read-only)
D. CRUD actions for Entities

Question #4
What is NOT a best practice for Mobile Application Architecture: Limit server side calls?

A. 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.
B. Direct calls is bad from Security, Performance and Maintainability standpoint. Direct calls will require javascript Code and javascript Code is harder to maintain.
C. 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.

Question #5
What is the common naming convention for a mobile version of a CS module?

A. M_CS
B. m_cs
C. mobile_CS
D. _CS
E. m_CS

Solutions: