OutSystems Architecture-Specialist-11 問題集

質問 1：
_BL module is for
A. Reusable Core Services with public entities, actions, and blocks.
B. A BL becomes a Calculation Engine if it performs complex calculations, (e.g. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.
C. Logic to Synchronize data in CS's with an external system. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.
D. Isolated Business Logic (Actions), to manage complexity, composition or to have its own 'ifecycle.
E. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
正解：D

質問 2：
Which of the following Data elements can we find in a End-User layer Module?
A. CRUD actions for Entities
B. Entities to save UI states
C. Non-core Entities
D. Core Entities (exposed as read-only)
正解：B

質問 3：
Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation
A. ... Entity is exposed as read-only and API is available to centralize business logic for entity ^ creation/update
B. ... 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
C. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
D. ... 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
E. ... 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.
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. 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
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. ... 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.
正解：H

質問 4：
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. ECS Summary cache only variation
B. Library : Connector Pattern
C. Transparency Service Pattern 1 way (simplification)
D. Base ECS pattern
E. Library : Extension Pattern
F. ECS with direct integration
G. ECS Lazy Load variation
H. Transparency Service Pattern
I. ECS with publish/subscribe through an ESB
J. ECS with isolated synchronization logic
正解：H

質問 5：
Which are NOT part of the major concepts that needs to be investigated in the Disclose phase in Architecture Design Process?
A. User Experience Expectations
B. Information Architecture
C. Integration Technology
D. Architecture Canvas Modules
E. User Stories, Personas and Roles
正解：D