New (2025) Download free Architecture-Specialist-11 PDF for OutSystems Practice Tests
100% Free Architecture-Specialist-11 Files For passing the exam Quickly
NEW QUESTION # 29
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. 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. ... 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)
- G. ... 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
- 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 exposed as read-only and API is available to centralize business logic for entity creation/update
- J. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
Answer: B
NEW QUESTION # 30
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. Transparency Service Pattern 1 way (simplification)
- B. ECS with publish/subscribe through an ESB
- C. Library : Connector Pattern
- D. Base ECS pattern
- E. ECS Lazy Load variation
- F. Transparency Service Pattern
- G. ECS Summary cache only variation
- H. ECS with direct integration
- I. Library : Extension Pattern
- J. ECS with isolated synchronization logic
Answer: F
NEW QUESTION # 31
Consider the following Module names and the suggested naming conventions for Modules. Which of these is a mobile Module?
- A. Customer_CW
- B. Pricing_MBL
- C. Mobile_API
- D. Service_CS
Answer: B
NEW QUESTION # 32
Concepts are assembled into Modules in the Assembl are not principles in the Assemble step.
- A. Don't join concepts with different lifecycles
- B. N/A
- C. Isolate reusable logic from Integration logic
- D. Join conceptually-related concepts
- E. Apply known design patterns
Answer: B
NEW QUESTION # 33
Foundation may have non-business services and business services in them
- A. TRUE
- B. FALSE
Answer: B
NEW QUESTION # 34
In which Architecture Canvas layer do you expect to have a higher reusability rate?
- A. Core layer
- B. Foundation layer
- C. End-User layer
Answer: B
NEW QUESTION # 35
Which of the below is NOT a suitable advice for designing a Parallel mobile local storage?
- A. Avoid generic tables : Contains too much data, not all are relevant
- B. Allow table dependency : Normalize tables to promote parallel data fetch
- C. Use Fetch Data : Avoid cascading aggregates in Onlnitialize and OnReady
Answer: B
NEW QUESTION # 36
Which of the below is not part of the Architecture Validation Rules?
- A. Don't Mix Owners
- B. Layer Applications Correctly
- C. Don't Mix Sponsers : Split the Apps based on the Lines of Business
- D. Layer Entities Correctly
- E. Layer Modules Correctly
Answer: D
NEW QUESTION # 37
Which of the below is NOT a disadvantage of having a fragmented system or microservices?
- A. Multiple transactions committed independently
- B. Fault tolerance : communication errors, service consistency
- C. Limited data mashup in memory and limited to APIs
- D. All of the above
- E. Complicated Debugging and troubleshooting : root cause may be deep inside the chain of services
- F. Monitoring & Logging : for effective monitoring & logging, requires centralized service
- G. Inter-process communication : network latency and hiccups
- H. Security : need to manage credentials and access management
Answer: D
NEW QUESTION # 38
Which of the below is NOT a Synchronization Best Practice for mobile application?
- A. Only synchronize delta : Use control timestamps
C Avoid long synchronization in a single transaction - B. Do not use Entity Bulk Operation to ensure small lightweight updates
- C. Sync only when required. p At session start: sync summary data to local storage At process start: sync process detail to local storage At process/transaction end, sync back to server
- D. Only synchronize relevant data
- E. Ensure sync granularity: Prepare for constant retries without repeating work due to network loss. Sync in chunks, incremental by entity
- F. Sync only when strictly required
E Don't sync on every screen or online event
Answer: F
NEW QUESTION # 39
OAPI is different compared to API. What is inside an OAPI?
- A. REST API
- B. Service Action
Answer: B
NEW QUESTION # 40
Which of the following is NOT a benefit of having well-defined application architecture?
- A. Reduces costs
- B. Supports planning
- C. Reduces risk
- D. Poor service abstraction
Answer: D
NEW QUESTION # 41
Which of the below are not recommendations for Architecture Validations
- A. No front-end screens in Core Modules
- B. No core entities in Foundational Modules
- C. No business logic in the Foundational Modules
- D. No screens in the End User Layer
- E. All public entities in Core Modules should be set to Read-only
Answer: D
NEW QUESTION # 42
_Lib module is for
- A. Theme, look & feel elements, menu, etc.
- B. Generic Library module
- C. Technical wrapper to consume and normalize an external service
- D. Reusable UI Patterns for layout and display only - no Business logic.
- E. Reusable Core Services with public entities, actions, and blocks.
- F. have several integration services with different systems, performing the same type of O operation (e.g. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).
Answer: B
NEW QUESTION # 43
Which of the below matches the most to Library Module Pattern - Connector 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 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
- C. ... 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.
- 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. 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. ... 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)
- 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- I. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- J. ... 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
Answer: A
NEW QUESTION # 44
_IS module is for
- A. Generic Library module.
- B. Theme, look & feel elements, menu, etc.
- C. 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).
- D. Reusable UI Patterns for layout and display only - no Business logic.
- E. technical wrapper to consume and normalize an external service.
Answer: E
NEW QUESTION # 45
Which of the below matches the most to Core Module Pattern - ECS with Local Replica Pattern...
- A. ... 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
- B. ... 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
- C. ... 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 - 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. ... 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. ... 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)
- 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- I. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
Answer: B
NEW QUESTION # 46
Architecture Canvas has 3 layers. Which is not part of the 3 layer framework?
- A. Core
- B. Foundation
- C. Ochestrator
- D. End-User Layer
Answer: C
NEW QUESTION # 47
What is NOT a best practice for Mobile Application Architecture: transactions & granularity?
- A. Have long synchronizations in a single transaction. Better UX as app does not need to sync all the time. Is prepared for constant offline or device standby
- B. Ensure order and sync granularity. Sync incrementally by entity with partial commit. This way O synchronizations is prepared for constant interruptions and allow retries without repeating the entire synchronization from the start.
Answer: A
NEW QUESTION # 48
Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation
- A. ... 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.
- 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. ... 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. ... 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. 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 synchronization logic is separated. Pro: Code independence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS
- H. ... 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
- 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: B
NEW QUESTION # 49
_Eng 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. 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. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, compositio or to have its own lifecycle.
Answer: C
NEW QUESTION # 50
Considering Discovery, which of the following sentences is FALSE?
- A. Discovery cannot categorise modules to domains
- B. Discovery allows you to determine for every module, which elements are being consumed by other modules.
- C. Discovery only validates architecture rules at the module level.
- D. Discovery automatically assigns a module to an Architecture Canvas layer, following the module's naming convention.
Answer: C
NEW QUESTION # 51
Which of the below matches the most to Core Module Pattern - ECS with Direct Integration Pattern
- A. 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)
- B. ... 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 - 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. ... 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. ... 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)
- G. ... 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
- H. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- I. . 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
- 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 # 52
Considering Architecture Dashboard(AI Mentor), which of the following sentences is FALSE?
- A. Architecture Dashboard performs a code analysis that uncovers patterns related to performance, security, architecture and maintainability.
- B. Architecture Dashboard allows you to automatically apply a solution to solve a found code pattern.
Answer: B
NEW QUESTION # 53
......
Architecture-Specialist-11 Premium Exam Engine - Download Free PDF Questions: https://www.testpassed.com/Architecture-Specialist-11-still-valid-exam.html
Architecture-Specialist-11 Dumps Questions Study Exam Guide : https://drive.google.com/open?id=1jcfCHjjUS2h6diV_yFhG4U5-4CuLgumQ