OutSystems Architecture Specialist (OutSystems 11) - Architecture-Specialist-11 FREE EXAM DUMPS QUESTIONS & ANSWERS

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

A. It identifies possible performance bottlenecks. B. It optimizes lifecycle independence. C. It promotes a correct abstraction of reusable services. D. It minimizes the impact of changes.

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

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

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. Same as ECS with direct integration, but through an Enterprise Service Bus C. ... tries to fetch data from local cache entity, if not there, get single entry from the external p 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 D. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data. 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. ... is a pattern with two modules, a connector module that can be used to encapsulate an O external API with the input/output structures and a wrapper module to expose the normalized API to the consumers. G. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update H. 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) I. ... 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 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

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

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. ... 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 C. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data. D. ... 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. E. ... Entity is exposed as read-only and API is available to centralize business logic for entity ^ creation/update 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. ... tries to fetch data from local cache entity, if not there, get single entry from the external p 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. ... Entity is not in Outsystems but in an external ERP system. IS just makes remote call to . 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. 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. 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

A. N/A B. Isolate reusable logic from Integration logic C. Don't join concepts with different lifecycles D. Join conceptually-related concepts E. Apply known design patterns

A. framework to support Architecture Conventions for Modules in Outsystems B. framework to support Architecture Design Process in Outsystems C. framework to support application architecture design in Outsystems