OutSystems Architecture-Specialist-11 問題集

質問 1：
ISO/IEC 9126:1991 included several different dimensions. Which is NOT part of ISO/IEC 9126:1991?
A. Usability : Usability from the point of view of the users
B. Security : Security which relates to the strength of the of the software against cybersecurity attacks
C. Maintainability : Maintainability which relates to the effort needed to make modifications
D. Reliability : Reliability which ensures that a software solution can maintain it performance over a period of time
E. Efficiency : Efficiency which relates to the performance to the amount of resources used
F. Functionality : Functionality as a set of functions that satisfy needs
G. Portability : Portability which defines the ability to move software between environments
正解：B

質問 2：
Which of the below is NOT a reason for adopting Naming Conventions for Modules
A. Enforce the reference architecture
B. Normalize known patterns
C. Reveal nature of each module
D. Ensure it belongs to the correct layer
正解：D

質問 3：
_Th module is for
A. technical wrapper to consume and normalize an external service.
B. to have several integration services with different systems, performing the same type of operation (e.g. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).
C. Reusable UI Patterns for layout and display only - no Business logic.
D. Theme, look & feel elements, menu, etc.
E. Generic Library module.
正解：D

質問 4：
There are generally 4 common style guide scenario. Which of the below is NOT a common style guide scenario?
A. Since the theme is very basic, front-end developer will have to expand and design the theme from there.
Modify Built-in Style Guide: Use when only small changes are required for single application. First, create a custom theme that REFERENCE the Base Theme. Second, clone a Custom Template from the Base Template but this custom theme will reference the custom theme created previously. Third, reference that application to the custom Theme and Template.
B. Built-in Style Guide: Uses Built-in style guide from Outsystems UI. Minor customizations to the Base Theme should be done inside the App Theme.
C, Build Your Own: Use when custom style guide cannot benefit from any existing theme. Just like Clone a Built In scenario, clone both Custom Theme and Custom Template from the Base Theme and Base Template, however clone the Base Theme from Outsystems UI.
C. Specialize a Built-in: Use when introducing changes to an existing theme for multiple apps. First, create a custom theme that REFERENCE the Base Theme. Second, clone a Custom Template from the Base Template but this custom theme will reference the custom theme created previously. Third, create new applications based on the Custom Theme and Custom Template
D. Clone a Built-in: Use when introducing extensive changes to existing theme. First, CLONE a custom theme from a Base Theme. Second, clone a Custom Template from the Base Template but this custom theme will reference the custom theme created previously. Third, create new applications based on the Custom Theme and Custom Template.Base Theme can be Outsystems UI or your own custom theme.
正解：A

質問 5：
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