最新のArchitecture-Specialist-11問題集で試験を準備する

Adopting a naming convention can have some benefits. Of the sentences below, which one is NOT a benefit of adopting a naming convention?

• A. Enforce the reference architecture.
• B. Normalize patterns.
• C. Reveal the nature of each Module.
• D. Avoid error codes.

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

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

Regarding Validation Rules for application composition, which of the following sentences is correct?

• A. Applications in the Foundation layer can reference Applications in the End-user layer.
• B. If you follow all the rules for validating modules, your application composition will be sound, and easy to maintain and deploy.
• C. Owners of the Application should not be mixed, but mixing Sponsors has no direct impact on the release.
• D. Common modules and services should be isolated in a separate app that can be referenced by other apps.

"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. Blocks grouped in functional modules with independent life cycles
• B. Include the Common flow and Menu artifacts
• C. Put CSS in blocks or screens. Allows better performance and seamless screen transitions
• D. CSS should only be placed in the mobile theme module
• E. Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.