Architecture-Specialist-11 Dumps PDF 2024 Strategy Your Preparation Efficiently [Q26-Q44]

Rate this post

Architecture-Specialist-11 Dumps PDF 2024 Strategy Your Preparation Efficiently

Latest Verified & Correct OutSystems Architecture-Specialist-11 Questions

Q26. Which of the following is NOT a benefit of having well-defined application architecture?

Poor service abstraction

Reduces costs

Reduces risk

Supports planning

Q27. _BL module is for

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.

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.

Isolated Business Logic (Actions), to manage complexity, composition or to have its own ‘ifecycle.

Reusable Core Services with public entities, actions, and blocks.

Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.

Q28. ISO/IEC 9126:1991 included several different dimensions. Which is NOT part of ISO/IEC 9126:1991?

Usability : Usability from the point of view of the users

Efficiency : Efficiency which relates to the performance to the amount of resources used

Portability : Portability which defines the ability to move software between environments

Security : Security which relates to the strength of the of the software against cybersecurity attacks

Reliability : Reliability which ensures that a software solution can maintain it performance over a period of time

Maintainability : Maintainability which relates to the effort needed to make modifications

Functionality : Functionality as a set of functions that satisfy needs

Q29. “Spaghetti Architecture” is also known as ‘tightly coupled architecture’ or ‘brittle architecture’. Which is NOT a reason why is “Spaghetti Architecture” bad?

One small change in a component cause a series of cascading effects on other components

Hinder future changes as they become less flexible and difficult to manage

Any changes is maintainable and easy to deploy

Q30. Which of the below best matches this statement : “Needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.”

Transparency Service Pattern 1 way (simplification)

Library : Extension Pattern

ECS with isolated synchronization logic

ECS Lazy Load variation

ECS with publish/subscribe through an ESB

ECS Summary cache only variation

Library : Connector Pattern

ECS with direct integration

Base ECS pattern

Transparency Service Pattern

Q31. Which of the below are FALSE about UI framework?

Patterns – are blocks that provide common and reusable UI. Chat message, date picker and carousel are a few examples. Contains reusable UI components.

All of the above are true

Theme – for the look and feel of your applications, which includes screen layouts, global stylesheet and grid definitions. Contains CSS styles and classes.

Templates – Defines the structure of the application modules. Templates contains screen p definitions and basic set of functionalities, including authentication.

Q32. “Splitting UI elements per functionality” is a best practice to avoid monolithic mobile UI modules? Which of the below is not a best practice?

Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.

Include the Common flow and Menu artifacts

Put CSS in blocks or screens. Allows better performance and seamless screen transitions

Blocks grouped in functional modules with independent life cycles

CSS should only be placed in the mobile theme module

Q33. Which of the following is an Assembling principle?

Isolate all business concepts.

Disclose business concepts and integration needs.

Keep concepts with different lifecycles apart.

Join all integrations into a single Module.

Q34. Which are NOT part of the major concepts that needs to be investigated in the Disclose phase in Architecture Design Process?

User Experience Expectations

Integration Technology

User Stories, Personas and Roles

Architecture Canvas Modules

Information Architecture

Q35. Which of the following options denotes the advantages of defining a Style Guide up front?

Security and scalability.

Speed up the development phase.

Improve performance and maintainability.

Allows apps and the Style Guide to be deployed to Production.

Q36. What does NOT happen due to a lack of architecture concerns?

Inflexible and slow-moving legacy systems : adapting legacy systems to business changes may be difficult. Changes in complex and inflexible systems can take a long time

Tech Debt : AI Mentor will raise architectural tech debt such as cyclic dependency and side to side dependency

Unmanageable dependencies : System not isolated from each other. Updating or replacing a system has a cascade/snowball effect on other systems

Poor service abstraction : Business concepts not correctly isolated, business rules tend to be spread over different systems and little to no code reuse

Q37. What is done in the Organize part of the Architecture Design Process?

Concepts are disclosed to the Architecture team

Concepts are assembled into Modules

Concepts are added to the layers of the Architecture Canvas

Q38. _Eng module is for

Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, compositio or to have its own lifecycle.

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.

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.

Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.

Reusable Core Services with public entities, actions, and blocks.

Q39. What is the common naming convention for a mobile version of a CS module?

M_CS

_CS

mobile_CS

m_cs

m_CS

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

Do not use local storage(mobile device), instead try to use central storage(server side)

Map server side static entities into local entities

Have a local storage inside the CS Module instead of M_CS Module

Use a centralized local storage for all mobile applications to ensure maintainability

Q41. Which of the below matches the most to Core Module Pattern – ECS with Publish/Subscribe through ESB…

… Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

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

Same as ECS with direct integration, but through an Enterprise Service Bus

… 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.

… 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

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)

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

… 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

… 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

… is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

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

Layer Applications Correctly

Don’t Mix Sponsers : Split the Apps based on the Lines of Business

Layer Entities Correctly

Layer Modules Correctly

Don’t Mix Owners

Q43. _Pat module is for

Generic Library module.

Reusable UI Patterns for layout and display only – no Business logic.

Theme, look & feel elements, menu, etc.

technical wrapper to consume and normalize an external service.

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).

Q44. Which of the below matches the most to Core Module Pattern – ECS Lazy Load variation

… 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)

… 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.

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

… Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

… 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

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)

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

… 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

… is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

… 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

Architecture-Specialist-11 PDF Dumps Are Helpful To produce Your Dreams Correct QA’s: https://www.real4dumps.com/Architecture-Specialist-11_examcollection.html

Architecture-Specialist-11 Dumps PDF 2024 Strategy Your Preparation Efficiently [Q26-Q44]

Leave a Reply Cancel reply