OutSystems Architecture Specialist 11 Architecture Specialist (OutSystems 11) Online Training
OutSystems Architecture Specialist 11 Online Training
The questions for Architecture Specialist 11 were last updated at Apr 15,2025.
- Exam Code: Architecture Specialist 11
- Exam Name: Architecture Specialist (OutSystems 11)
- Certification Provider: OutSystems
- Latest update: Apr 15,2025
Concepts are assembled into Modules in the Assembl are not principles in the Assemble step.
- A . Don’t join concepts with different lifecycles
- B . Apply known design patterns
- C . N/A
- D . Join conceptually-related concepts
- E . Isolate reusable logic from Integration logic
In OutSystems, a Core Application can contain …
- A . End-User, Core, and Foundation Modules.
- B . Foundation and Core Modules
- C . Only Foundation Modules.
- D . End-User and Core Modules.
"Spaghetti Architecture" is also known as ‘tightly coupled architecture’ or ‘brittle architecture’.
Which is NOT a reason why is "Spaghetti Architecture" bad?
- A . One small change in a component cause a series of cascading effects on other components
- B . Hinder future changes as they become less flexible and difficult to manage
- C . Any changes is maintainable and easy to deploy
Which of the below is NOT a reason for Validating a Modules’ Architecture?
- A . Optimizes lifecycle independence
- B . Promotes microservices
- C . Minimizes impact of changes
- D . Promotes abstraction of reusable services
- E . Stop unmanageable dependencies
- F . Prevent slow deployments, inflexible legacy systems
- G . Avoid poor service abstraction
Elements such as the menu and login can be shared across different apps. In the menu and login are defined inside the theme.
Which use case is this?
- A . Portal
- B . Intranet
- C . Independent Apps
Which of the below best matches this statement: "Needed if data is coming from MULTIPLE external systems.
IS will decide which driver to use depending on the data."
- A . Transparency Service Pattern 1 way (simplification)
- B . Library: Extension Pattern
- C . ECS with isolated synchronization logic
- D . ECS Lazy Load variation
- E . ECS with publish/subscribe through an ESB
- F . ECS Summary cache only variation
- G . Library: Connector Pattern
- H . ECS with direct integration
- I . Base ECS pattern
- J . Transparency Service Pattern
In which Architecture Canvas layer do you expect to have a higher reusability rate?
- A . End-User layer
- B . Core layer
- C . Foundation layer
In OutSystems, a Foundation Application can NOT contain …
- A . Core Modules and Foundation Modules.
- B . End-User and Foundation Modules.
- C . End-user and Core Modules.
Which of the below matches the most to Core Module Pattern – Core Entity Pattern…
- A . is a pattern with two modules, a connector module that can be used to encapsulate an O external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.
- 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 . … Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- E . 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 - F . 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)
- G . … 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
- 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 synchronization logic is separated. Pro: Code independence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS
- J . … 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
Which of the below is not a best practice for mobile security: authentication?
- A . Store password in local storage
- B . Encrypt (only) sensitive data
- C . Authentication: Use google or facebook for online authentication or fingerprint or pin for offline authentication