Free OutSystems Architecture-Specialist Exam Questions

Try our Free Demo Practice Tests for Comprehensive Architecture-Specialist Exam Preparation

OutSystems Architecture-Specialist Exam Questions
Provided By: OutSystems
Exam: Architecture Specialist (OutSystems 11)
Certification: OutSystems Certification

Total Questions: 85
Updated On: Nov 20, 2024
Rated: 4.9 |
Online Users: 170

Page No. 1 of 17

Add To Cart

Question 1
- _Sync module is for
  
  A : Reusable Core Services with public entities, actions, and blocks.
  
  B :
  Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
  
  C :
  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.
  
  D :
  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.
  
  E :
  Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
  
  Answer: D
Question 2
- Which of the below matches the most to Core Module Pattern - ECS with Publish/Subscribe through ESB...
  
  A :
  ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
  
  B :
  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
  
  C : Same as ECS with direct integration, but through an Enterprise Service Bus
  
  D :
  ... 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.
  
  E :
  ... 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
  
  F :
  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)
  
  G :
  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
  
  H :
  ... 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
  
  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 :
  ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
  
  Answer: C
Question 3
- What is done in the Organize part of the Architecture Design Process?
  
  A : Concepts are disclosed to the Architecture team
  
  B : Concepts are assembled into Modules
  
  C : Concepts are added to the layers of the Architecture Canvas
  
  Answer: C
Question 4
- 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: Code independence. 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
  
  Answer: J
Question 5
- Which of the below matches the most to Core Module Pattern - ECS with Publish/Subscribe through ESB...
  
  A :
  ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
  
  B :
  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
  
  C : Same as ECS with direct integration, but through an Enterprise Service Bus
  
  D :
  ... 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.
  
  E :
  ... 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
  
  F :
  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)
  
  G :
  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
  
  H :
  ... 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
  
  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 :
  ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
  
  Answer: C

PAGE: 1 - 17

Add To Cart

We use cookies to ensure your best experience. So we hope you are happy to receive all cookies on the Dumpscity.