Download OutSystems Architecture-Specialist-11 Exam Dumps to Pass Exam Easily in 2025
Get 100% Real Free Architecture Specialization Architecture-Specialist-11 Sample Questions
NEW QUESTION # 32
Which of the below is NOT a reason why application Architecture is important when building quality software solutions?
- A. Drives Consensus : Helps create common ground with the team
- B. Reduces Costs : Architecture benefits are not only technical, but affect how you operate
- C. Reduces Risk : Architecture is a cost effective way to mitigate substantial risks and ensure ^ success
- D. 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.
- E. Manages Complexity : Helps reduce emerging complexity by focusing on relevant properties and omitting irrelevant details, thus leading to simpler representation
- F. Helps Communication : Helps you to get buy in from the business and to communicate overall plan to them
- G. Supports Planning : Helps the team anticipate and build solutions
Answer: F
NEW QUESTION # 33
Which of the following is a benefit of having good architecture?
- A. Slow-moving legacy systems
- B. Poor service abstraction
- C. Unmanageable dependencies
- D. Manages complexity
Answer: D
NEW QUESTION # 34
Which are NOT part of the major concepts that needs to be investigated in the Disclose phase in Architecture Design Process?
- A. Integration Technology
- B. User Stories, Personas and Roles
- C. Information Architecture
- D. Architecture Canvas Modules
- E. User Experience Expectations
Answer: D
NEW QUESTION # 35
_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. 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: E
NEW QUESTION # 36
_Th module is for
- A. technical wrapper to consume and normalize an external service.
- B. 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).
- C. Theme, look & feel elements, menu, etc.
- D. Reusable UI Patterns for layout and display only - no Business logic.
- E. Generic Library module.
Answer: C
NEW QUESTION # 37
ISO/IEC 9126:1991 included several different dimensions. Which is NOT part of ISO/IEC 9126:1991?
- A. Portability : Portability which defines the ability to move software between environments
- B. Reliability : Reliability which ensures that a software solution can maintain it performance over a period of time
- C. Efficiency : Efficiency which relates to the performance to the amount of resources used
- D. Functionality : Functionality as a set of functions that satisfy needs
- E. Usability : Usability from the point of view of the users
- F. Security : Security which relates to the strength of the of the software against cybersecurity attacks
- G. Maintainability : Maintainability which relates to the effort needed to make modifications
Answer: F
NEW QUESTION # 38
Which of the below matches the most to Core Module Pattern - ECS with Publish/Subscribe through ESB...
- A. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- B. 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
- C. Same as ECS with direct integration, but through an Enterprise Service Bus
- D. ... 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
- E. ... 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
- F. ... 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.
- G. 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)
- 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- J. ... 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
Answer: C
NEW QUESTION # 39
Which of the below matches the most to Core Module Pattern - ECS with Direct Integration Pattern
- A. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- B. 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
- C. ... 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)
- 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- F. 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)
- 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. ... 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 - J. ... 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
Answer: F
NEW QUESTION # 40
Which of the below are FALSE about UI framework?
- A. Patterns - are blocks that provide common and reusable UI. Chat message, date picker and carousel are a few examples. Contains reusable UI components.
- B. Templates - Defines the structure of the application modules. Templates contains screen p definitions and basic set of functionalities, including authentication.
- C. Theme - for the look and feel of your applications, which includes screen layouts, global stylesheet and grid definitions. Contains CSS styles and classes.
- D. All of the above are true
Answer: D
Explanation:
Contains common layouts, menu, login and reference to the theme .
NEW QUESTION # 41
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."
- A. ECS with isolated synchronization logic
- B. ECS with publish/subscribe through an ESB
- C. Transparency Service Pattern
- D. Library : Connector Pattern
- E. Transparency Service Pattern 1 way (simplification)
- F. Library : Extension Pattern
- G. ECS with direct integration
- H. Base ECS pattern
- I. ECS Summary cache only variation
- J. ECS Lazy Load variation
Answer: C
NEW QUESTION # 42
Which of the below is not part of the Architecture Validation
- A. No Side References Between End-User Modules
- B. No Circular References
- C. No Upward References
- D. No Downward References To Foundation Modules
Answer: D
NEW QUESTION # 43
Adopting a naming convention can have some benefits. Of the sentences below, which one is NOT a benefit of adopting a naming convention?
- A. Enforce the reference architecture.
- B. Avoid error codes.
- C. Reveal the nature of each Module.
- D. Normalize patterns.
Answer: B
NEW QUESTION # 44
Foundation may have non-business services and business services in them
- A. TRUE
- B. FALSE
Answer: B
NEW QUESTION # 45
What is a best practice for Mobile Application Architecture: Local Storage?
- A. Have a local storage inside the CS Module instead of M_CS Module
- B. Do not use local storage(mobile device), instead try to use central storage(server side)
- C. Map server side static entities into local entities
- D. Use a centralized local storage for all mobile applications to ensure maintainability
Answer: C
NEW QUESTION # 46
Which of the following recommendations should be applied to the Core layer?
- A. Core modules should not have business logic.
- B. Core modules should not have Core Entities.
- C. Core modules should have public Read-only Entities.
- D. Core modules should have Front-end Screens for testing purposes.
Answer: C
NEW QUESTION # 47
What is NOT a best practice for Mobile Application Architecture: Local Storage?
- A. Sync data required per use case: Sync summary data on Session start. On data selection, sync p its details.
- B. Sync on every screen or online event
- C. Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online
Answer: B
Explanation:
Example: if you are accessing Purchasing data, sync the summary data on Session start. On selecting the Purchasing item, sync the details of the Purchasing item such as photos or price, a
NEW QUESTION # 48
There are 3 common scenarios for Sharing a Style Guide. Which of the below is not part of th scenario.
- A. 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.
- B. Enterprise Apps: Common Menu, Common Login Flow. Menu is defined in the Custom Theme, but Login is defined in the Custom Template.
- C. 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.
- D. 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.
Answer: B
NEW QUESTION # 49
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. It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.
- C. When minor customizations to the base theme should be done inside the app theme.
- D. When you want to introduce extensive changes to an existing theme.
Answer: D
NEW QUESTION # 50
Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation
- 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. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- C. ... 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)
- D. ... 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
- E. ... 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.
- 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. 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)
- 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. ... 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity ^ creation/update
Answer: C
NEW QUESTION # 51
Which of the below is NOT a reason for Validating a Modules' Architecture?
- A. Avoid poor service abstraction
- B. Stop unmanageable dependencies
- C. Promotes abstraction of reusable services
- D. Promotes microservices
- E. Minimizes impact of changes
- F. Prevent slow deployments, inflexible legacy systems
- G. Optimizes lifecycle independence
Answer: D
NEW QUESTION # 52
What is the common naming convention for a mobile version of a CS module?
- A. m_CS
- B. m_cs
- C. _CS
- D. mobile_CS
- E. M_CS
Answer: A
NEW QUESTION # 53
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. Encrypt (only) sensitive data
- C. Store password in local storage
Answer: C
NEW QUESTION # 54
Which of the below is NOT a suitable advice for designing a LIGHTWEIGHT mobile local storage?
- A. Denormalize the local storage
- B. Store all records no matter if relevant or irrelevant
- C. Define only used attributes
- D. Group relevant information
Answer: B
NEW QUESTION # 55
......
Architecture-Specialist-11 Study Guide Realistic Verified Dumps: https://www.actual4dump.com/OutSystems/Architecture-Specialist-11-actualtests-dumps.html
Accurate Architecture-Specialist-11 Questions with Free and Fast Updates: https://drive.google.com/open?id=1bVot5NtYLS--OhyWkpV9dY9dYknslOds