Architecture-Specialist-11 無料問題集「OutSystems Architecture Specialist (OutSystems 11)」

（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）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.

（C）Direct calls is bad from Security, Performance and Maintainability standpoint. Direct calls will require javascript Code and javascript Code is harder to maintain.

（A）Multiple transactions committed independently

（B）Monitoring & Logging : for effective monitoring & logging, requires centralized service

（C）Inter-process communication : network latency and hiccups

（D）Complicated Debugging and troubleshooting : root cause may be deep inside the chain of services

（E）Limited data mashup in memory and limited to APIs

（F）Security : need to manage credentials and access management

（G）All of the above

（H）Fault tolerance : communication errors, service consistency

（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）Generic Library module.

（C）Theme, look & feel elements, menu, etc.

（D）Reusable UI Patterns for layout and display only - no Business logic.

（E）technical wrapper to consume and normalize an external service.

（A）Isolate all business concepts.

（B）Join all integrations into a single Module.

（C）Keep concepts with different lifecycles apart.

（D）Disclose business concepts and integration needs.

（A）framework to support Architecture Conventions for Modules in Outsystems

（B）framework to support application architecture design in Outsystems

（C）framework to support Architecture Design Process in Outsystems

（A）Patterns - are blocks that provide common and reusable UI. Chat message, date picker and carousel are a few examples. Contains reusable UI components.

（B）Theme - for the look and feel of your applications, which includes screen layouts, global stylesheet and grid definitions. Contains CSS styles and classes.

（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.

（A）Allows apps and the Style Guide to be deployed to Production.

（B）Security and scalability.

（C）Speed up the development phase.

（D）Improve performance and maintainability.

（A）ECS Summary cache only variation

（B）ECS with isolated synchronization logic

（C）ECS with direct integration

（D）ECS with publish/subscribe through an ESB

（E）Transparency Service Pattern 1 way (simplification)

（F）Library : Connector Pattern

（G）Base ECS pattern

（H）ECS Lazy Load variation

（I）Transparency Service Pattern

（J）Library : Extension Pattern