Pass exam with Architecture-Specialist-11 Top Exam Collection for sure one-shot

OutSystems Architecture-Specialist-11 Exam Overview:

OutSystems Architecture-Specialist-11 Exam Syllabus Topics:

OutSystems Architecture Specialist (OutSystems 11) Sample Questions:

Question 1

Which of the below is NOT a suitable advice for designing a Parallel mobile local storage?

A. Use Fetch Data : Avoid cascading aggregates in Onlnitialize and OnReady
B. Allow table dependency : Normalize tables to promote parallel data fetch
C. Avoid generic tables : Contains too much data, not all are relevant

Question 2

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

A. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
B. 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)
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. ... 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
E. ... 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
F. ... 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)
G. ... 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
H. 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
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. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

Question 3

_Th module is for

A. 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).
B. Generic Library module.
C. Reusable UI Patterns for layout and display only - no Business logic.
D. technical wrapper to consume and normalize an external service.
E. Theme, look & feel elements, menu, etc.

Question 4

Which of the following is an Assembling principle?

A. Isolate all business concepts.
B. Join all integrations into a single Module.
C. Keep concepts with different lifecycles apart.
D. Disclose business concepts and integration needs.

Question 5

Which of the below matches the most to Core Module Pattern - ECS with Direct Integration Pattern

A. ... 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
B. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
C. 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)
D. . 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
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. ... 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)
G. ... 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.
H. ... 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
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 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

Solutions: