2025 100% Free Architecture-Specialist-11 Daily Practice Exam With 85 Questions [Q49-Q73]

Share

2025 100% Free Architecture-Specialist-11 Daily Practice Exam With 85 Questions

Architecture-Specialist-11 exam torrent OutSystems study guide

NEW QUESTION # 49
What is the Architecture Blueprint?

  • A. Is the end result of Architecture Design Process. At this point you should add dependencies between the Modules.
  • B. Above is the answer

Answer: A


NEW QUESTION # 50
Which of the following is a benefit of having good architecture?

  • A. Manages complexity
  • B. Unmanageable dependencies
  • C. Poor service abstraction
  • D. Slow-moving legacy systems

Answer: A


NEW QUESTION # 51
Of the options below, which one is a benefit of adopting the Architecture Canvas?

  • A. It's an automatic way to find and fix architecture issues.
  • B. It's a faster architecture design
  • C. It promotes the business users' collaboration and understanding
  • D. It's a systematic approach to architecture design

Answer: D


NEW QUESTION # 52
CS modules 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. 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.
  • C. Reusable Core Services with public entities, actions, and blocks.
  • D. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
  • 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: C


NEW QUESTION # 53
OAPI is different compared to API. What is inside an OAPI?

  • A. REST API
  • B. Service Action

Answer: B


NEW QUESTION # 54
Which of the below matches the most to Core Module Pattern - ECS with Isolated Synchronization Logic 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 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
  • C. 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)
  • D. 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
  • E. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
  • 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. ... 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
  • H. ... 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)
  • I. ... 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
  • J. ... 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

Answer: B


NEW QUESTION # 55
What does NOT happen due to a lack of architecture concerns?

  • A. Tech Debt : AI Mentor will raise architectural tech debt such as cyclic dependency and side to side dependency
  • B. Poor service abstraction : Business concepts not correctly isolated, business rules tend to be spread over different systems and little to no code reuse
  • C. Unmanageable dependencies : System not isolated from each other. Updating or replacing a system has a cascade/snowball effect on other systems
  • D. 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

Answer: A


NEW QUESTION # 56
What is Application Composition Process?

  • A. Answer is the above.
  • B. Process to package modules into apps

Answer: B


NEW QUESTION # 57
"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. Blocks grouped in functional modules with independent life cycles
  • D. Put CSS in blocks or screens. Allows better performance and seamless screen transitions
  • E. Include the Common flow and Menu artifacts

Answer: D


NEW QUESTION # 58
Which of the below is NOT a suitable advice for designing a LIGHTWEIGHT mobile local storage?

  • A. Store all records no matter if relevant or irrelevant
  • B. Denormalize the local storage
  • C. Define only used attributes
  • D. Group relevant information

Answer: A


NEW QUESTION # 59
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. Have a local storage inside the CS Module instead of M_CS Module
  • D. Use a centralized local storage for all mobile applications to ensure maintainability

Answer: A


NEW QUESTION # 60
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 publish/subscribe through an ESB
  • B. ECS with direct integration
  • C. Transparency Service Pattern
  • D. Base ECS pattern
  • E. ECS Lazy Load variation
  • F. ECS Summary cache only variation
  • G. Library : Extension Pattern
  • H. Library : Connector Pattern
  • I. Transparency Service Pattern 1 way (simplification)
  • J. ECS with isolated synchronization logic

Answer: C


NEW QUESTION # 61
Concepts are assembled into Modules in the Assembl are not principles in the Assemble step.

  • A. Don't join concepts with different lifecycles
  • B. Join conceptually-related concepts
  • C. Apply known design patterns
  • D. Isolate reusable logic from Integration logic
  • E. N/A

Answer: E


NEW QUESTION # 62
Which is not a reason you should use Architecture Canvas?

  • A. Promotes abstraction of reusable services
  • B. Minimizes impact of changes
  • C. Optimizes lifecycle independence
  • D. Promotes segregation and loose coupling of services

Answer: D


NEW QUESTION # 63
Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation

  • A. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
  • B. ... 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)
  • C. 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)
  • D. 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
  • 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. ... 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity ^ creation/update
  • 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. ... 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.
  • J. 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

Answer: B


NEW QUESTION # 64
_Sync 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. 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.
  • C. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
  • 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: B


NEW QUESTION # 65
Consider the common style guide scenarios presented in this course. Which of the following statements is true?

  • A. The "specialize a built-in Style Guide" scenario should be used when the changes to the base theme are not extensive.
  • B. The "clone a built-in Style Guide" should be used when you want to extend an existing theme.
  • C. Build-your-own Style Guide should be used when the changes in the theme are not extensive.

Answer: A


NEW QUESTION # 66
SSL Pinning is a security best practice for mobile application. Which of the below is FALSE about SSL Pinning?

  • A. 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
  • B. All of the above are true
  • C. SSL Pinning or HTTP Public Key Pinning (HPKP) helps reduce man-in-the-middle attacks
  • D. SSL Pinning does not mean hardcoding the public key into the code.

Answer: D


NEW QUESTION # 67
What is NOT a best practice for Mobile Application Architecture: Limit server side calls?

  • A. 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.
  • B. Direct calls is bad from Security, Performance and Maintainability standpoint. Direct calls will require javascript Code and javascript Code is harder to maintain.
  • 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: A


NEW QUESTION # 68
_IS module is for

  • A. 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).
  • B. technical wrapper to consume and normalize an external service.
  • C. Reusable UI Patterns for layout and display only - no Business logic.
  • D. Generic Library module.
  • E. Theme, look & feel elements, menu, etc.

Answer: B


NEW QUESTION # 69
_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 # 70
What is NOT a best practice for Mobile Application Architecture: Local Storage?

  • A. Sync on every screen or online event
  • B. Sync data required per use case: Sync summary data on Session start. On data selection, sync p its details.
  • C. Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online

Answer: A

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 # 71
Which of the below matches the most to Library Module Pattern - Connector Pattern...

  • A. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
  • 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. 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)
  • D. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
  • E. ... 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
  • 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. ... 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. ... 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. ... 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. 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

Answer: F


NEW QUESTION # 72
In OutSystems, an application with Foundation, Core, and End-User Modules is a

  • A. Core Application.
  • B. Foundation Application.
  • C. End-User Application.

Answer: C


NEW QUESTION # 73
......

Use Valid New Architecture-Specialist-11 Test Notes & Architecture-Specialist-11 Valid Exam Guide: https://www.examdiscuss.com/OutSystems/exam/Architecture-Specialist-11/

Architecture-Specialist-11 Actual Questions Answers PDF 100% Cover Real Exam Questions: https://drive.google.com/open?id=1mju3Ip_XvE3Vqs31takvYNB3Zmxhcd3w

0
0
0
10