Pass with professional Architecture-Specialist-11 actual quiz materials

OutSystems Architecture-Specialist-11 Exam Overview:

OutSystems Architecture-Specialist-11 Exam Syllabus Topics:

OutSystems Architecture Specialist (OutSystems 11) Sample Questions:

1. Which of the following Data elements can we find in a End-User layer Module?

A) Non-core Entities
B) CRUD actions for Entities
C) Core Entities (exposed as read-only)
D) Entities to save UI states

2. _Eng module is for

A) Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
B) Logic to Synchronize data in CS's with an external system. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.
C) Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, compositio or to have its own lifecycle.
D) Reusable Core Services with public entities, actions, and blocks.
E) A BL becomes a Calculation Engine if it performs complex calculations, (e.g. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.

3. Which of the following Data elements can we find in a Foundation layer Module?

A) Non-core Entities
B) CRUD actions for Entities
C) Core Entities (exposed as read-only)
D) Entities to save UI states

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

A) ... 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
B) ... 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.
C) . 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
D) ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
E) ... 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)
F) ... 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
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) 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) ... 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

5. Which of the below is not part of the Architecture Validation Rules?

A) Layer Modules Correctly
B) Don't Mix Sponsers : Split the Apps based on the Lines of Business
C) Layer Entities Correctly
D) Layer Applications Correctly
E) Don't Mix Owners

Solutions: