Guaranteed Accomplishment with Newest Sep-2025 FREE OutSystems Architecture-Specialist-11
Use Valid New Free Architecture-Specialist-11 Exam Dumps & Answers
NEW QUESTION # 16
"Splitting UI elements per functionality" is a best practice to avoid monolithic mobile UI modules? Which of the below is not a best practice?
- A. Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.
- B. CSS should only be placed in the mobile theme module
- C. Put CSS in blocks or screens. Allows better performance and seamless screen transitions
- D. Include the Common flow and Menu artifacts
- E. Blocks grouped in functional modules with independent life cycles
Answer: C
NEW QUESTION # 17
The Architecture Canvas is a multi-layer framework. Which of the following is NOT a benefit of this framework?
- A. It promotes a correct abstraction of reusable services.
- B. It minimizes the impact of changes.
- C. It optimizes lifecycle independence.
- D. It identifies possible performance bottlenecks.
Answer: D
NEW QUESTION # 18
_Sync module is for
- A. Reusable Core Services with public entities, actions, and blocks.
- B. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- 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. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
- 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: E
NEW QUESTION # 19
OAPI is different compared to API. What is inside an OAPI?
- A. Service Action
- B. REST API
Answer: A
NEW QUESTION # 20
_API module is for
- A. Reusable Core Services with public entities, actions, and blocks.
- B. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- 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. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
- 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: B
NEW QUESTION # 21
Elements such as the menu and login can be shared across different apps. In the menu and login are defined inside the theme. Which use case is this?
- A. Independent Apps
- B. Portal
- C. Intranet
Answer: B
NEW QUESTION # 22
Consider the common style guide scenarios presented in this course. Which of the following statements is true?
- A. Build-your-own Style Guide should be used when the changes in the theme are not extensive.
- B. The "specialize a built-in Style Guide" scenario should be used when the changes to the base theme are not extensive.
- C. The "clone a built-in Style Guide" should be used when you want to extend an existing theme.
Answer: B
NEW QUESTION # 23
Consider the following Module names and the suggested naming conventions for Modules. Which of these is a mobile Module?
- A. Pricing_MBL
- B. Service_CS
- C. Customer_CW
- D. Mobile_API
Answer: A
NEW QUESTION # 24
Which of the following is an Assembling principle?
- A. Keep concepts with different lifecycles apart.
- B. Isolate all business concepts.
- C. Disclose business concepts and integration needs.
- D. Join all integrations into a single Module.
Answer: A
NEW QUESTION # 25
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 # 26
Which of the below is NOT a reason for adopting Naming Conventions for Modules
- A. Ensure it belongs to the correct layer
- B. Reveal nature of each module
- C. Enforce the reference architecture
- D. Normalize known patterns
Answer: A
NEW QUESTION # 27
What is a best practice for Mobile Application Architecture: Local Storage?
- A. Map server side static entities into local entities
- B. Do not use local storage(mobile device), instead try to use central storage(server side)
- C. Use a centralized local storage for all mobile applications to ensure maintainability
- D. Have a local storage inside the CS Module instead of M_CS Module
Answer: A
NEW QUESTION # 28
Adopting a naming convention can have some benefits. Of the sentences below, which one is NOT a benefit of adopting a naming convention?
- A. Reveal the nature of each Module.
- B. Enforce the reference architecture.
- C. Normalize patterns.
- D. Avoid error codes.
Answer: D
NEW QUESTION # 29
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 # 30
Which of the below matches the most to Core Module Pattern - Core Entity Pattern...
- 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. 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. ... 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. ... 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 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
- G. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- 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.
- 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: C
NEW QUESTION # 31
Which of the below is NOT a reason why application Architecture is important when building quality software solutions?
- A. Helps Communication : Helps you to get buy in from the business and to communicate overall plan to them
- B. Reduces Risk : Architecture is a cost effective way to mitigate substantial risks and ensure ^ success
- C. Reduces Costs : Architecture benefits are not only technical, but affect how you operate
- D. Supports Planning : Helps the team anticipate and build solutions
- E. Drives Consensus : Helps create common ground with the team
- F. Manages Complexity : Helps reduce emerging complexity by focusing on relevant properties and omitting irrelevant details, thus leading to simpler representation
- 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: A
NEW QUESTION # 32
The Architecture Canvas is a ...
- A. framework to support Architecture Design Process in Outsystems
- B. framework to support Architecture Conventions for Modules in Outsystems
- C. framework to support application architecture design in Outsystems
Answer: C
NEW QUESTION # 33
Which of the below matches the most to Library Module Pattern - Connector Pattern...
- 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. ... 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
- 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. ... 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
- 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- H. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- 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. 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: I
NEW QUESTION # 34
In which of the following scenarios should you choose to clone a built-in Style Guide?
- A. When minor customizations to the base theme should be done inside the app theme.
- B. When it is not possible to benefit from any existing theme and extensive changes are needed.
- C. It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.
- D. When you want to introduce extensive changes to an existing theme.
Answer: D
NEW QUESTION # 35
Which of the below matches the most to Core Module Pattern - Base ECS Pattern...
- 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. ... 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.
- C. 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
- 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. ... 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 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
- G. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- H. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- 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. ... 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: B
NEW QUESTION # 36
What is NOT a best practice for Mobile Application Architecture: Limit server side calls?
- A. Direct calls is bad from Security, Performance and Maintainability standpoint. Direct calls will require javascript Code and javascript Code is harder to maintain.
- B. 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. - 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: B
NEW QUESTION # 37
Which of the below is NOT part of the three step process of Architecture Design Process?
- A. Disclose
- B. Organize
- C. Shape
- D. Assemble
Answer: C
NEW QUESTION # 38
......
Architecture-Specialist-11 Braindumps PDF, OutSystems Architecture-Specialist-11 Exam Cram: https://examtorrent.dumpsactual.com/Architecture-Specialist-11-actualtests-dumps.html
