OutSystems Architecture-Specialist-11 試験概要:

OutSystems Architecture-Specialist-11 試験シラバストピック:

OutSystems Architecture Specialist (OutSystems 11) 認定 Architecture-Specialist-11 試験問題：

問題 #1
Architecture Canvas has 3 layers. Which is not part of the 3 layer framework?

A. Foundation
B. Ochestrator
C. End-User Layer
D. Core

問題 #2
Which of the following is NOT a benefit of having well-defined application architecture?

A. Reduces costs
B. Reduces risk
C. Supports planning
D. Poor service abstraction

問題 #3
In OutSystems, an application with Foundation, Core, and End-User Modules is a

A. Foundation Application.
B. End-User Application.
C. Core Application.

問題 #4
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. ... 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
C. ... 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.
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. ... 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. 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
H. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
I. ... 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)
J. 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)

問題 #5
Which of the below are not recommendations for Architecture Validations

A. No screens in the End User Layer
B. No front-end screens in Core Modules
C. All public entities in Core Modules should be set to Read-only
D. No business logic in the Foundational Modules
E. No core entities in Foundational Modules

解説：