First Attempt Guaranteed Success in Architecture-Specialist-11 Exam 2024 [Q28-Q47]

First Attempt Guaranteed Success in Architecture-Specialist-11 Exam 2024

Real Architecture-Specialist-11 Exam Questions are the Best Preparation Material

NEW QUESTION # 28
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 # 29
Which of the below matches the most to Library Module Pattern - Connector Pattern...

• 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. 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 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. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
• 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 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
• H. ... 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
• 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

Answer: J

NEW QUESTION # 30
Which of the following Data elements can we find in a End-User layer Module?

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

Answer: C

NEW QUESTION # 31
In OutSystems, a Foundation Application can NOT contain ...

• A. Core Modules and Foundation Modules.
• B. End-user and Core Modules.
• C. End-User and Foundation Modules.

Answer: B

NEW QUESTION # 32
CS modules is for

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

Answer: A

NEW QUESTION # 33
What is NOT a best practice for Mobile Application Architecture: Limit server side calls?

• A. Synchronize on every screen or online event for better granularity
  No direct calls to backend systems. Do call to Outsystems Core Services and Outsystems will handle the interaction with external backend systems.
• B. Direct calls is bad from Security, Performance and Maintainability standpoint. Direct calls will require javascript Code and javascript Code is harder to maintain.
• C. Limit Server side calls to online transactions or Synchronization. Do the bulk of the operations on the Client Side before passing information to the Server Side.

Answer: A

NEW QUESTION # 34
Which of the below is not a best practice for mobile security:authentication?

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

Answer: B

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

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

Answer: C

NEW QUESTION # 36
In OutSystems, an application with Foundation, Core, and End-User Modules is a

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

Answer: B

NEW QUESTION # 37
"Spaghetti Architecture" is also known as 'tightly coupled architecture' or 'brittle architecture'. Which is NOT a reason why is "Spaghetti Architecture" bad?

• A. Any changes is maintainable and easy to deploy
• B. Hinder future changes as they become less flexible and difficult to manage
• C. One small change in a component cause a series of cascading effects on other components

Answer: A

NEW QUESTION # 38
Which of the below matches the most to Core Module Pattern - ECS with Local Replica Pattern...

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

Answer: E

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

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

Answer: A

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

• A. 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.
• B. 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.
• C. 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
• D. 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.
  C, 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.

Answer: B

NEW QUESTION # 41
Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation

• 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. ... 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 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. 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. ... 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.
• I. ... 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
• J. 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)

Answer: E

NEW QUESTION # 42
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 cannot categorise modules to domains
• C. Discovery allows you to determine for every module, which elements are being consumed by other modules.
• D. Discovery only validates architecture rules at the module level.

Answer: D

NEW QUESTION # 43
Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation

• A. ... 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
• B. ... 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)
• 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. ... 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. ... 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 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. 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 i 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 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)

Answer: G

NEW QUESTION # 44
_Eng 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, compositio 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. Reusable Core Services with public entities, actions, and blocks.

Answer: C

NEW QUESTION # 45
_CW module is for

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

Answer: C

NEW QUESTION # 46
Which of the below is NOT a reason why application Architecture is important when building quality software solutions?

• A. Reduces Risk : Architecture is a cost effective way to mitigate substantial risks and ensure ^ success
• B. Drives Consensus : Helps create common ground with the team
• C. Manages Complexity : Helps reduce emerging complexity by focusing on relevant properties and omitting irrelevant details, thus leading to simpler representation
• D. Supports Planning : Helps the team anticipate and build solutions
• E. Reduces Costs : Architecture benefits are not only technical, but affect how you operate
• F. Helps Communication : Helps you to get buy in from the business and to communicate overall plan to them
• G. Facilitate Change : When something comes up that requires you to veer from the origina design or path, architecture of your system can show you exactly what needs to change and help with communication and planning.

Answer: F

NEW QUESTION # 47
......

Practice LATEST Architecture-Specialist-11 Exam Updated 85 Questions: https://prepaway.vcetorrent.com/Architecture-Specialist-11-valid-vce-torrent.html