OutSystems
Architecture-Specialist-11
Q1:
Consider the common style guide scenarios presented in this course. Which of the following statements is true?
○
A
The 'specialize a built-in Style Guide' scenario should be used when the changes to the base theme are not extensive.○
B
The 'clone a built-in Style Guide' should be used when you want to extend an existing theme.○
C
Build-your-own Style Guide should be used when the changes in the theme are not extensive.
OutSystems
Architecture-Specialist-11
Q2:
Which of the below matches the most to Core Module Pattern - ECS with Isolated Synchronization Logic Pattern...
○
A
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○
B
... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update○
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 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○
E
... 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)○
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
... 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○
H
... 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.○
I
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)○
J
... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
OutSystems
Architecture-Specialist-11
Q3:
Which of the below matches the most to Library Module Pattern - Connector Pattern...
○
A
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)○
B
... 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○
C
Same as ECS with local replica but synchronization logic is separated. Pro: Codeindependence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS
○
D
... 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)○
E
... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update○
F
... 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○
G
... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.○
H
... tries to fetch data from local cache entity, if not there, get single entry from the external n 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○
I
... 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.○
J
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
OutSystems
Architecture-Specialist-11
Q4:
Themes and Layouts are an important element of an application. In which of the following would you define these elements?
○
A
MyApp_CS Module, in the Foundation layer○
B
MyApp_BL, in the Foundation Layer.○
C
MyApp_Th Module, in the End-User layer○
D
MyApp_MTh, in the Foundation layer.
OutSystems
Architecture-Specialist-11
Q5:
What is the common naming convention for a mobile version of a CS module?
○
A
M_CS○
B
_CS○
C
mobile_CS○
D
m_cs○
E
m_CS