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

1. In which of the following scenarios should you choose to clone a built-in Style Guide?

A) It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.
B) When you want to introduce extensive changes to an existing theme.
C) When minor customizations to the base theme should be done inside the app theme.
D) When it is not possible to benefit from any existing theme and extensive changes are needed.

2. Which of the below matches the most to Core Module Pattern - ECS with Isolated Synchronization Logic Pattern...

A) ... 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.
B) ... caches only summary data that is frequently lister, joined or searched. Full detail for a O 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)
C) ... a wrapper used to contain the logic, actions and data that will expose code that is inside of O external library or to inspect external database and import the data structures so they can be used as entities inside of OS
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) 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
F) ... Entity is not in Outsystems but in an external ERP system. IS just makes remote call to p 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 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) ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
I) ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
J) ... tries to fetch data from local cache entity, if not there, get single entry from the external v 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

3. What is NOT a best practice for Mobile Application Architecture: Local Storage?

A) Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online
B) Sync data required per use case: Sync summary data on Session start. On data selection, sync p its details.
C) Sync on every screen or online event

4. In which Architecture Canvas layer do you expect to have a higher reusability rate?

A) Core layer
B) Foundation layer
C) End-User layer

5. What is the new name for Architecture Dashboard?

A) Architecture Validation
B) AI Mentor
C) Architecture Canvas
D) Architecture Framework

質問と回答：