Free OutSystems Architecture-Specialist-11 Exam Dumps Questions

A. have several integration services with different systems, performing the same type of O operation (e.

B. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).

C. Technical wrapper to consume and normalize an external service

D. Reusable Core Services with public entities, actions, and blocks.

E. Theme, look & feel elements, menu, etc.

F. Generic Library module

G. Reusable UI Patterns for layout and display only - no Business logic.

A. Poor service abstraction

B. Reduces costs

C. Reduces risk

D. Supports planning

A. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, compositio or to have its own lifecycle.

B. Logic to Synchronize data in CS's with an external syste

C. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.

D. A BL becomes a Calculation Engine if it performs complex calculations, (e.

E. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.

F. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.

G. Reusable Core Services with public entities, actions, and blocks.

A. Do not use local storage(mobile device), instead try to use central storage(server side)

B. Map server side static entities into local entities

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

A. Common modules and services should be isolated in a separate app that can be referenced by other apps.

B. Owners of the Application should not be mixed, but mixing Sponsors has no direct impact on the release.

C. If you follow all the rules for validating modules, your application composition will be sound, and easy to maintain and deploy.

D. Applications in the Foundation layer can reference Applications in the End-user layer.

A. Keep concepts with different lifecycles apart.

B. Join all integrations into a single Module.

C. Disclose business concepts and integration needs.

D. Isolate all business concepts.