Reliable Architecture Specialization Architecture-Specialist-11 Dumps PDF Oct 17, 2025 Recently Updated Questions
Pass Your OutSystems Architecture-Specialist-11 Exam with Correct 85 Questions and Answers
NEW QUESTION # 13
What does NOT happen due to a lack of architecture concerns?
- A. Poor service abstraction : Business concepts not correctly isolated, business rules tend to be spread over different systems and little to no code reuse
- B. Tech Debt : AI Mentor will raise architectural tech debt such as cyclic dependency and side to side dependency
- C. 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
- D. Unmanageable dependencies : System not isolated from each other. Updating or replacing a system has a cascade/snowball effect on other systems
Answer: B
NEW QUESTION # 14
Which of the below matches the most to Core Module Pattern - ECS with Isolated Synchronization Logic Pattern...
- A. 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
- B. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- C. ... caches only summary data that is frequently lister, joined or searched. Full detail for a O 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. 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
- E. ... 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.
- F. ... 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
- 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. ... tries to fetch data from local cache entity, if not there, get single entry from the external v 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. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- J. ... 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
Answer: D
NEW QUESTION # 15
_CW 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. 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. Reusable Core Services with public entities, actions, and blocks.
- 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. Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
Answer: E
NEW QUESTION # 16
Which is not a reason you should use Architecture Canvas?
- A. Promotes segregation and loose coupling of services
- B. Optimizes lifecycle independence
- C. Minimizes impact of changes
- D. Promotes abstraction of reusable services
Answer: A
NEW QUESTION # 17
Which of the below matches the most to Core Module Pattern - ECS with Publish/Subscribe through ESB...
- A. 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
- B. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- C. ... 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
- D. Same as ECS with direct integration, but through an Enterprise Service Bus
- 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. ... 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
- G. ... 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.
- 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. ... 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. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
Answer: D
NEW QUESTION # 18
What is a best practice for Mobile Application Architecture: Local Storage?
- A. Map server side static entities into local entities
- B. Use a centralized local storage for all mobile applications to ensure maintainability
- C. Do not use local storage(mobile device), instead try to use central storage(server side)
- D. Have a local storage inside the CS Module instead of M_CS Module
Answer: A
NEW QUESTION # 19
SSL Pinning is a security best practice for mobile application. Which of the below is FALSE about SSL Pinning?
- A. SSL Pinning or HTTP Public Key Pinning (HPKP) helps reduce man-in-the-middle attacks
- B. Works on the client side and adds verification of the server certificate against hashes of public keys, which are pre-bundled with the mobile app
- C. All of the above are true
- D. SSL Pinning does not mean hardcoding the public key into the code.
Answer: D
NEW QUESTION # 20
What is NOT a best practice for Mobile Application Architecture: Local Storage?
- A. Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online
- B. Sync data required per use case: Sync summary data on Session start. On data selection, sync p its details.
- C. Sync on every screen or online event
Answer: C
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 # 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. Portal
- B. Independent Apps
- C. Intranet
Answer: A
NEW QUESTION # 22
The Architecture Canvas is a multi-layer framework. Which of the following is NOT a benefit of this framework?
- A. It identifies possible performance bottlenecks.
- B. It promotes a correct abstraction of reusable services.
- C. It optimizes lifecycle independence.
- D. It minimizes the impact of changes.
Answer: A
NEW QUESTION # 23
Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation
- A. ... Entity is exposed as read-only and API is available to centralize business logic for entity ^ creation/update
- B. ... 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
- 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. ... 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.
- 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. ... 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. ... 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)
- 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. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
Answer: G
NEW QUESTION # 24
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. It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.
- C. When you want to introduce extensive changes to an existing theme.
- D. When it is not possible to benefit from any existing theme and extensive changes are needed.
Answer: C
NEW QUESTION # 25
ISO/IEC 25010:2011 adds two more aspect to ISO/IEC 9126:1991. Which of the below is not part of it?
- A. Integration : Integration to allow data exchange with other software
- B. Security : Security ensure software solutions can protect information and data
- C. Compatibility : Compatibility was also added as a way to ensure that a piece of software can work together with other systems
Answer: A
NEW QUESTION # 26
"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. CSS should only be placed in the mobile theme module
- B. Put CSS in blocks or screens. Allows better performance and seamless screen transitions
- C. Include the Common flow and Menu artifacts
- D. Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.
- E. Blocks grouped in functional modules with independent life cycles
Answer: B
NEW QUESTION # 27
Foundation may have non-business services and business services in them
- A. FALSE
- B. TRUE
Answer: A
NEW QUESTION # 28
Which of the below matches the most to Core Module Pattern - Base ECS 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. 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. 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
- E. ... 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
- F. ... 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
- 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. ... 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)
- I. ... 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
- J. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
Answer: A
NEW QUESTION # 29
In OutSystems, a Core Application can contain ...
- A. Only Foundation Modules.
- B. Foundation and Core Modules
- C. End-User and Core Modules.
- D. End-User, Core, and Foundation Modules.
Answer: B
NEW QUESTION # 30
Which of the below matches the most to Core Module Pattern - ECS with Local Replica Pattern...
- A. ... 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
- 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. ... 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 - E. ... 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
- 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. ... 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)
- H. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- 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
Answer: A
NEW QUESTION # 31
......
Latest 2025 Realistic Verified Architecture-Specialist-11 Dumps: https://actualtests.prep4away.com/OutSystems-certification/braindumps.Architecture-Specialist-11.ete.file.html