Valid Architecture-Specialist-11 Exam Dumps Ensure you a HIGH SCORE (2024)
Pass Architecture-Specialist-11 Exam with Latest Questions
NEW QUESTION # 50
Which of the below are not recommendations for Architecture Validations
- A. No core entities in Foundational Modules
- B. All public entities in Core Modules should be set to Read-only
- C. No screens in the End User Layer
- D. No business logic in the Foundational Modules
- E. No front-end screens in Core Modules
Answer: C
NEW QUESTION # 51
In which Architecture Canvas layer do you expect to have a higher reusability rate?
- A. End-User layer
- B. Foundation layer
- C. Core layer
Answer: B
NEW QUESTION # 52
OAPI is different compared to API. What is inside an OAPI?
- A. Service Action
- B. REST API
Answer: A
NEW QUESTION # 53
What is Application Composition Process?
- A. Process to package modules into apps
- B. Answer is the above.
Answer: A
NEW QUESTION # 54
Which is not a reason you should use Architecture Canvas?
- A. Promotes segregation and loose coupling of services
- B. Minimizes impact of changes
- C. Promotes abstraction of reusable services
- D. Optimizes lifecycle independence
Answer: A
NEW QUESTION # 55
_API module is for
- A. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
- 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. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- 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: C
NEW QUESTION # 56
What is the common naming convention for a mobile version of a CS module?
- A. m_cs
- B. _CS
- C. mobile_CS
- D. m_CS
- E. M_CS
Answer: D
NEW QUESTION # 57
Which of the below matches the most to Library Module Pattern - Extension Pattern...
- A. ... 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
- 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. 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. 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)
- 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 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 not in Outsystems but in an external ERP system. IS just makes remote call to v 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 ) 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 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: A
NEW QUESTION # 58
Which of the following is an Assembling principle?
- A. Disclose business concepts and integration needs.
- B. Join all integrations into a single Module.
- C. Keep concepts with different lifecycles apart.
- D. Isolate all business concepts.
Answer: C
NEW QUESTION # 59
In the Architecture Canvas, where should the API module sit in?
- A. Core Layer
- B. Foundation Layer
- C. End-User Layer
Answer: A
NEW QUESTION # 60
Themes and Layouts are an important element of an application. In which of the following would you define these elements?
- A. MyApp_MTh, in the Foundation layer.
- B. MyApp_BL, in the Foundation Layer.
- C. MyApp_CS Module, in the Foundation layer
- D. MyApp_Th Module, in the End-User layer
Answer: D
NEW QUESTION # 61
Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation
- A. ... 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)
- 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. ... 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
- D. ... a wrapper used to contain the logic, actions and data that will expose code that is inside of i 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 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
- 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- H. ... 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.
- 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: B
NEW QUESTION # 62
Which of the below is not part of the Architecture Validation
- A. No Circular References
- B. No Side References Between End-User Modules
- C. No Upward References
- D. No Downward References To Foundation Modules
Answer: D
NEW QUESTION # 63
Which of the below matches the most to Core Module Pattern - ECS with Isolated Synchronization Logic 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 O external library or to inspect external database and import the data structures so they can be used as entities inside of OS
- C. ... 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
- 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. 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)
- F. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- 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 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
- I. ... 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)
- 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 # 64
"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. Blocks grouped in functional modules with independent life cycles
- E. Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.
Answer: B
NEW QUESTION # 65
Which of the below are FALSE about UI framework?
- A. Theme - for the look and feel of your applications, which includes screen layouts, global stylesheet and grid definitions. Contains CSS styles and classes.
- B. Patterns - are blocks that provide common and reusable UI. Chat message, date picker and carousel are a few examples. Contains reusable UI components.
- C. All of the above are true
- D. Templates - Defines the structure of the application modules. Templates contains screen p definitions and basic set of functionalities, including authentication.
Answer: C
Explanation:
Contains common layouts, menu, login and reference to the theme .
NEW QUESTION # 66
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
- B. ECS Summary cache only variation
- C. Library : Extension Pattern
- D. ECS with direct integration
- E. Transparency Service Pattern 1 way (simplification)
- F. ECS with publish/subscribe through an ESB
- G. ECS Lazy Load variation
- H. ECS with isolated synchronization logic
- I. Library : Connector Pattern
- J. Base ECS pattern
Answer: A
NEW QUESTION # 67
......
Architecture-Specialist-11 Exam Practice Questions prepared by OutSystems Professionals: https://prep4sure.dumpstests.com/Architecture-Specialist-11-latest-test-dumps.html