Regular Free Updates Architecture-Specialist-11 Dumps Real Exam Questions Test Engine Jan 17, 2024 [Q32-Q55]

4.5/5 - (2 votes)

Regular Free Updates Architecture-Specialist-11 Dumps Real Exam Questions Test Engine Jan 17, 2024

Practice Test Questions Verified Answers As Experienced in the Actual Test!

Q32. Concepts are assembled into Modules in the Assembl are not principles in the Assemble step.

Don’t join concepts with different lifecycles

Apply known design patterns

N/A

Join conceptually-related concepts

Isolate reusable logic from Integration logic

Q33. Of the options below, which one is a benefit of adopting the Architecture Canvas?

It’s an automatic way to find and fix architecture issues.

It’s a systematic approach to architecture design

It promotes the business users’ collaboration and understanding

It’s a faster architecture design

Q34. _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.

Q35. “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

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

Core modules should have Front-end Screens for testing purposes.

Core modules should not have Core Entities.

Core modules should have public Read-only Entities.

Core modules should not have business logic.

Q37. Which is not a reason you should use Architecture Canvas?

Promotes segregation and loose coupling of services

Optimizes lifecycle independence

Promotes abstraction of reusable services

Minimizes impact of changes

Q38. Which of the following Data elements can we find in a Foundation layer Module?

CRUD actions for Entities

Core Entities (exposed as read-only)

Non-core Entities

Entities to save UI states

Q39. Foundation may have non-business services and business services in them

TRUE

FALSE

Q40. Which of the below is NOT a suitable advice for designing a Parallel mobile local storage?

Allow table dependency : Normalize tables to promote parallel data fetch

Use Fetch Data : Avoid cascading aggregates in Onlnitialize and OnReady

Avoid generic tables : Contains too much data, not all are relevant

Q41. There are 3 common scenarios for Sharing a Style Guide. Which of the below is not part of th scenario.

Intranet (Single Sign On): Own Menu, Common Login Flow. Menu is defined in the Custom Template, but Login is defined in the Custom Theme. Application reference the Custom Them which picks up the Login.

Enterprise Apps: Common Menu, Common Login Flow. Menu is defined in the Custom Theme, but Login is defined in the Custom Template.

Independent Apps : Own Menu, Own Login Flow. Login and Menu is defined in the Custom Template. Applications reference to its own Application Theme thus do not use the Login and Menu in the Custom Template.

Portal : Common Menu, Common Login Flow. Login and Menu is defined in the Custom Them Application Theme reference the Custom Theme thus have a shared menu and login flow.

Q42. Which of the below matches the most to Core Module Pattern – ECS with Local Replica Pattern…

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

… 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

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

… 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

… 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

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

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)

Q43. Which of the below is NOT a reason for Validating a Modules’ Architecture?

Optimizes lifecycle independence

Promotes microservices

Minimizes impact of changes

Promotes abstraction of reusable services

Stop unmanageable dependencies

Prevent slow deployments, inflexible legacy systems

Avoid poor service abstraction

Q44. Regarding Validation Rules for application composition, which of the following sentences is correct?

Common modules and services should be isolated in a separate app that can be referenced by other apps.

Owners of the Application should not be mixed, but mixing Sponsors has no direct impact on the release.

If you follow all the rules for validating modules, your application composition will be sound, and easy to maintain and deploy.

Applications in the Foundation layer can reference Applications in the End-user layer.

Q45. The Architecture Canvas is a multi-layer framework. Which of the following is NOT a benefit of this framework?

It optimizes lifecycle independence.

It identifies possible performance bottlenecks.

It minimizes the impact of changes.

It promotes a correct abstraction of reusable services.

Q46. Which of the below matches the most to Library Module Pattern – Connector Pattern…

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 exposed as read-only and API is available to centralize business logic for entity creation/update

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

… 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

… 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

Q47. Which of the below matches the most to Library Module Pattern – Extension Pattern…

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

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

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

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

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

… 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

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

Q48. Which of the below are not recommendations for Architecture Validations

All public entities in Core Modules should be set to Read-only

No business logic in the Foundational Modules

No core entities in Foundational Modules

No screens in the End User Layer

No front-end screens in Core Modules

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

Q50. CS modules is for

Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition 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.

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

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.

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

Q51. In which of the following scenarios should you choose to clone a built-in Style Guide?

When minor customizations to the base theme should be done inside the app theme.

It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.

When you want to introduce extensive changes to an existing theme.

When it is not possible to benefit from any existing theme and extensive changes are needed.

Q52. In OutSystems, a Core Application can contain …

End-User, Core, and Foundation Modules.

Foundation and Core Modules

Only Foundation Modules.

End-User and Core Modules.

Q53. _API module is for

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.

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

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

Q55. “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

Pass OutSystems Architecture-Specialist-11 Exam in First Attempt Easily: https://www.prepawaytest.com/OutSystems/Architecture-Specialist-11-practice-exam-dumps.html

Leave a Reply Cancel reply