QUESTION: 33

Which of the below are not recommendations for Architecture Validations

All public entities in Core Modules should be set to Read-only
No business logic in the Foundational Modules
No core entities in Foundational Modules
No screens in the End User Layer
No front-end screens in Core Modules

Answer(s): D

Reveal Solution Next Question

QUESTION: 34

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

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

Answer(s): A

Reveal Solution Next Question

QUESTION: 35

_API module is for

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.
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.
Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
Reusable Core Services with public entities, actions, and blocks.
Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.

Answer(s): C

Reveal Solution Next Question

QUESTION: 36

Which of the below matches the most to Library Module Pattern - Extension Pattern...

... 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.
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)
... 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
... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
... 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)
Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
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
Entity is not in Outsystems but in an external ERP system. IS just makes remote call to v 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
... 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
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

Answer(s): I

Reveal Solution Next Question

Free Architecture-Specialist-11 Exam Braindumps

QUESTION: 33

QUESTION: 34

QUESTION: 35

QUESTION: 36