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

OutSystems ARCHITECTURE-SPECIALIST-11 Online Questions & Answers

• Question 51:

  Consider the following Module names and the suggested naming conventions for Modules. Which of these is a mobile Module?

  A. Customer_CW
  B. Mobile_API
  C. Service_CS
  D. Pricing_MBL
  D. Pricing_MBL

  ---

  Explanation/Reference:

• Question 52:

  In the Architecture Canvas, where should the API module sit in?

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

• Question 53:

  SSL Pinning is a security best practice for mobile application. Which of the below is FALSE about SSL Pinning?

  A. Works on the client side and adds verification of the server certificate against hashes of public keys, which are pre-bundled with the mobile app.
  B. SSL Pinning or HTTP Public Key Pinning (HPKP) helps reduce man-in-the-middle attacks.
  C. SSL Pinning does not mean hardcoding the public key into the code.
  D. All of the above are true.
  C. SSL Pinning does not mean hardcoding the public key into the code.

  ---

  Explanation/Reference:

• Question 54:

  Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation?

  A. Same as Base ECS pattern, but has a local replica. Store data to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration API. Con: Less impact on the source system.
  B. caches only summary data that is frequently listed, joined, or searched. Full detail for a single entry is fetched directly from the external system. Use when the whole database is too big or costly to synchronize. Details are only required for single entities (not lists).
  C. Same as ECS with a local replica, but synchronization logic is separated. Pro: Code independence. Consumers of CS are not affected by Sync. Sync can orchestrate several CS.
  D. Same as ECS with a local replica, but the API module is provided. So any changes to the external system can notify OS, which then gets updates from the ERP system (subscription system).
  E. Entity is exposed as read-only, and an API is available to centralize business logic for entity creation/update.
  F. is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
  G. tries to fetch data from the local cache entity; if not there, gets a single entry from the external system. Cache only that record (read-through caching). Use when the whole database is 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.
  H. a wrapper used to contain the logic, actions, and data that will expose code inside an external library or inspect an external database and import the data structures so they can be used as entities inside OS.
  I. Entity is not in OutSystems but in an external ERP system. IS just makes remote calls to the 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 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. caches only summary data that is frequently listed, joined, or searched. Full detail for a single entry is fetched directly from the external system. Use when the whole database is too big or costly to synchronize. Details are only required for single entities (not lists).

  ---

  Explanation/Reference:

• Question 55:

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

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

• Question 56:

  Which of the below matches the most to Library Module Pattern - Extension 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. 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)
  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. 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. Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
  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 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
  I. 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
  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
  I. 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

  ---

  Explanation/Reference:

• Question 57:

  The Architecture Design Process has three steps. Which of the options below is NOT one of those steps?

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

• Question 58:

  There are generally 4 common style guide scenario. Which of the below is NOT a common style guide scenario?

  A. Specialize a Built-in: Use when introducing changes to an existing theme for multiple apps. First, create a custom theme that REFERENCE the Base Theme. Second, clone a Custom Template from the Base Template but this custom theme will reference the custom theme created previously. Third, create new applications based on the Custom Theme and Custom Template
  B. Built-in Style Guide: Uses Built-in style guide from Outsystems UI. Minor customizations to the Base Theme should be done inside the App Theme. Build Your Own: Use when custom style guide cannot benefit from any existing theme. Just like Clone a Built In scenario, clone both Custom Theme and Custom Template from the Base Theme and Base Template, however clone the Base Theme from Outsystems UI.
  C. Since the theme is very basic, front-end developer will have to expand and design the theme from there. Modify Built-in Style Guide: Use when only small changes are required for single application. First, create a custom theme that REFERENCE the Base Theme. Second, clone a Custom Template from the Base Template but this custom theme will reference the custom theme created previously. Third, reference that application to the custom Theme and Template.
  D. Clone a Built-in: Use when introducing extensive changes to existing theme. First, CLONE a custom theme from a Base Theme. Second, clone a Custom Template from the Base Template but this custom theme will reference the custom theme created previously. Third, create new applications based on the Custom Theme and Custom Template. Base Theme can be Outsystems UI or your own custom theme.
  D. Clone a Built-in: Use when introducing extensive changes to existing theme. First, CLONE a custom theme from a Base Theme. Second, clone a Custom Template from the Base Template but this custom theme will reference the custom theme created previously. Third, create new applications based on the Custom Theme and Custom Template. Base Theme can be Outsystems UI or your own custom theme.

  ---

  Explanation/Reference:

• Question 59:

  Which of the below is not a best practice for mobile security:authentication?

  A. Store password in local storage
  B. Encrypt (only) sensitive data
  C. Authentication : Use google or facebook for online authentication or fingerprint or pin for offline authentication
  A. Store password in local storage

• Question 60:

  Considering Discovery, which of the following sentences is FALSE?

  A. Discovery automatically assigns a module to an Architecture Canvas layer, following the module's naming convention.
  B. Discovery only validates architecture rules at the module level.
  C. Discovery allows you to determine for every module, which elements are being consumed by other modules.
  D. Discovery cannot categorise modules to domains
  B. Discovery only validates architecture rules at the module level.