2024 Valid Architecture-Specialist-11 FREE EXAM DUMPS QUESTIONS & ANSWERS [Q31-Q51]

Share

2024 Valid Architecture-Specialist-11 FREE EXAM DUMPS QUESTIONS & ANSWERS

Free Architecture-Specialist-11 Exam Braindumps OutSystems  Pratice Exam

NEW QUESTION # 31
ISO/IEC 9126:1991 included several different dimensions. Which is NOT part of ISO/IEC 9126:1991?

  • A. Reliability : Reliability which ensures that a software solution can maintain it performance over a period of time
  • B. Functionality : Functionality as a set of functions that satisfy needs
  • C. Maintainability : Maintainability which relates to the effort needed to make modifications
  • D. Security : Security which relates to the strength of the of the software against cybersecurity attacks
  • E. Portability : Portability which defines the ability to move software between environments
  • F. Efficiency : Efficiency which relates to the performance to the amount of resources used
  • G. Usability : Usability from the point of view of the users

Answer: D


NEW QUESTION # 32
Considering Discovery, which of the following sentences is FALSE?

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

Answer: D


NEW QUESTION # 33
_API module is for

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

Answer: A


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

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

Answer: B


NEW QUESTION # 35
Which of the below matches the most to Library Module Pattern - Extension Pattern...

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

Answer: A


NEW QUESTION # 36
Which of the below matches the most to Core Module Pattern - ECS with Direct Integration 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. . 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
  • C. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
  • D. ... 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
  • 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. ... 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.
  • G. ... 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
  • H. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
  • I. ... 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)
  • J. ... 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

Answer: A


NEW QUESTION # 37
Which of the below is NOT a suitable advice for designing a LIGHTWEIGHT mobile local storage?

  • A. Define only used attributes
  • B. Store all records no matter if relevant or irrelevant
  • C. Group relevant information
  • D. Denormalize the local storage

Answer: B


NEW QUESTION # 38
What is the Architecture Blueprint?

  • A. Is the end result of Architecture Design Process. At this point you should add dependencies between the Modules.
  • B. Above is the answer

Answer: A


NEW QUESTION # 39
Which of the following is a benefit of having good architecture?

  • A. Poor service abstraction
  • B. Slow-moving legacy systems
  • C. Manages complexity
  • D. Unmanageable dependencies

Answer: C


NEW QUESTION # 40
Which of the below is NOT a weak dependency as of OS11?

  • A. Static Entities
  • B. Screens
  • C. Service Actions
  • D. Structures
  • E. Database Entities
  • F. Local Storage Entities
  • G. Server Actions

Answer: G


NEW QUESTION # 41
Which of the below matches the most to Core Module Pattern - ECS with Isolated Synchronization Logic Pattern...

  • A. ... 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
  • 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
  • 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. 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
  • F. 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
  • G. ... 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
  • H. ... tries to fetch data from local cache entity, if not there, get single entry from the external v 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. ... caches only summary data that is frequently lister, joined or searched. Full detail for a O 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)
  • J. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

Answer: E


NEW QUESTION # 42
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.

Answer: A


NEW QUESTION # 43
Themes and Layouts are an important element of an application. In which of the following would you define these elements?

  • A. MyApp_BL, in the Foundation Layer.
  • B. MyApp_Th Module, in the End-User layer
  • C. MyApp_CS Module, in the Foundation layer
  • D. MyApp_MTh, in the Foundation layer.

Answer: B


NEW QUESTION # 44
Which of the below matches the most to Core Module Pattern - ECS with Publish/Subscribe through ESB...

  • A. ... 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
  • 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. ... 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
  • 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 direct integration, but through an Enterprise Service Bus
  • 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. 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
  • I. ... 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.
  • J. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

Answer: F


NEW QUESTION # 45
Which of the below matches the most to Core Module Pattern - Base ECS 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 exposed as read-only and API is available to centralize business logic for entity creation/update
  • C. ... 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
  • D. 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
  • E. 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
  • F. ... 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.
  • G. ... 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
  • H. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
  • I. ... 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)
  • 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

Answer: F


NEW QUESTION # 46
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 exposed as read-only and API is available to centralize business logic for entity creation/update
  • C. ... 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
  • 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. 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
  • F. ... 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
  • 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. 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
  • J. ... 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)

Answer: I


NEW QUESTION # 47
Which of the following Data elements can we find in a Foundation layer Module?

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

Answer: C


NEW QUESTION # 48
In which of the following scenarios should you choose to clone a built-in Style Guide?

  • A. When it is not possible to benefit from any existing theme and extensive changes are needed.
  • B. When you want to introduce extensive changes to an existing theme.
  • C. When minor customizations to the base theme should be done inside the app theme.
  • D. It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.

Answer: B


NEW QUESTION # 49
Consider the common style guide scenarios presented in this course. Which of the following statements is true?

  • A. The "clone a built-in Style Guide" should be used when you want to extend an existing theme.
  • B. The "specialize a built-in Style Guide" scenario should be used when the changes to the base theme are not extensive.
  • C. Build-your-own Style Guide should be used when the changes in the theme are not extensive.

Answer: B


NEW QUESTION # 50
The Architecture Canvas is a multi-layer framework. Which of the following is NOT a benefit of this framework?

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

Answer: B


NEW QUESTION # 51
......

Prepare For Realistic Architecture-Specialist-11 Dumps PDF - 100% Passing Guarantee: https://guidetorrent.dumpstorrent.com/Architecture-Specialist-11-exam-prep.html