OutSystems ARCHITECTURE-SPECIALIST-11 Online Practice Questions and Exam Preparation

OutSystems ARCHITECTURE-SPECIALIST-11 Online Questions & Answers

• Question 61:

  Which of the below is NOT part of the three step process of Architecture Design Process?

  A. Assemble
  B. Shape
  C. Disclose
  D. Organize
  B. Shape

• Question 62:

  Which of the below matches the most to Core Module Pattern - Base ECS Pattern?

  A. A wrapper used to contain the logic, actions, and data that will expose code inside an external library or to inspect an external database and import the data structures so they can be used as entities inside OS.
  B. Caches only summary data that is frequently listed, joined, or searched. Full details for a single entry are fetched directly from the external system. Use when: The whole database is too large or costly to synchronize, and details are only required for single entities (not lists).
  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. 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. is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
  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 Base ECS Pattern, but with a local replica. Data is stored to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration API. Con: Less impact on the source system.
  H. Entity is not in Outsystems but resides in an external ERP system. IS makes remote calls to the external system/database. No data is stored inside OS. Con: Data retrieval may not be optimized as it traverses two systems. Integration API must support all use cases.
  I. Attempts to fetch data from a local cache entity. If not found, it retrieves a single entry from the external system and caches only that record (read-through caching). Use when: The database is too large or costly to synchronize, and integration only requires a small portion of the data. Avoid if: Access to lists of data is needed upfront.
  J. Entity is exposed as read-only, and an API is available to centralize business logic for entity creation/update.
  D. 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.

  ---

  Explanation/Reference:

• Question 63:

  Which of the below matches the most to Core Module Pattern - Core Entity Pattern?

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

  ---

  Explanation/Reference:

• Question 64:

  Which is not a reason you should use Architecture Canvas?

  A. Promotes segregation and loose coupling of services
  B. Optimizes lifecycle independence
  C. Promotes abstraction of reusable services
  D. Minimizes impact of changes
  A. Promotes segregation and loose coupling of services

• Question 65:

  _Pat module is for

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

• Question 66:

  Considering Architecture Dashboard(AI Mentor), which of the following sentences is FALSE?

  A. Architecture Dashboard allows you to automatically apply a solution to solve a found code pattern.
  B. Architecture Dashboard performs a code analysis that uncovers patterns related to performance, security, architecture and maintainability.
  A. Architecture Dashboard allows you to automatically apply a solution to solve a found code pattern.

• Question 67:

  What is a best practice for Mobile Application Architecture: Local Storage?

  A. Do not use local storage(mobile device), instead try to use central storage(server side)
  B. Map server side static entities into local entities
  C. Have a local storage inside the CS Module instead of M_CS Module
  D. Use a centralized local storage for all mobile applications to ensure maintainability
  B. Map server side static entities into local entities

• Question 68:

  Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation

  A. 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)
  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 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
  D. Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
  E. 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
  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. 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. is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
  J. a wrapper used to contain the logic, actions and data that will expose code that is inside of i external library or to inspect external database and import the data structures so they can be used as entities inside of OS
  E. 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

  ---

  Explanation/Reference:

• Question 69:

  In OutSystems, an application with Foundation, Core, and End-User Modules is a

  A. End-User Application.
  B. Foundation Application.
  C. Core Application.
  A. End-User Application.

• Question 70:

  Which of the following recommendations should be applied to the Core layer?

  A. Core modules should have Front-end Screens for testing purposes.
  B. Core modules should not have Core Entities.
  C. Core modules should have public Read-only Entities.
  D. Core modules should not have business logic.
  C. Core modules should have public Read-only Entities.