ARCHITECTURE-SPECIALIST-11 practice question 10 of 15

Which of the below matches the most to Core Module Pattern - Base ECS Pattern...

Full set: 83 questions
Answer options
A:

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:

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:

C. 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:

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

Correct answer
E:

E. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

F:

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:

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:

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:

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

J:

J. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

Correct Answer:
D. D. ... 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.
Explanation

The Base ECS (Expose and Consume Services) pattern is a foundational integration strategy in OutSystems architecture. It mandates a two-module approach to ensure loose coupling and maintainability. It consists of:
1. A private Connector module that encapsulates the technical details of consuming an external API, including its specific data structures and actions. This module is tightly coupled to the external system.
2. A public Core Service (CS) or Wrapper module that consumes the Connector. This module provides a stable, simplified, and normalized API to the rest of the application. It isolates consumer modules from any changes or volatility in the external system's API. This separation of concerns is the core principle of the pattern.

Why Incorrect

A. This describes an Extension module, which is used to wrap custom C# code or connect to external databases, not the ECS module pattern.
B. This describes the "Cache Summary / Fetch Detail" pattern, a specific caching strategy built on top of an integration, not the base pattern itself.
C. This describes the "Sync Wrapper" pattern, an advanced pattern that separates synchronization logic from the core service module for better orchestration.
E. This describes a "Facade" or "Integration Service" pattern, which is used to abstract and orchestrate multiple underlying external systems.
F. This describes a reactive integration or subscription pattern, where the external system notifies OutSystems of changes, not the fundamental ECS structure.
G. This describes the "Local Replica" pattern, which explicitly adds a local data cache to the Base ECS pattern for performance or offline capabilities.
H. This describes the general concept of a remote call but misses the crucial two-module (Connector/Wrapper) structure that defines the ECS pattern.
I. This describes the "Read-Through Cache" pattern, a specific on-demand caching strategy, not the base integration structure.
J. This describes the standard pattern for a Core module that exposes its own entities and business logic, not an integration pattern.

References

1. OutSystems Official Documentation, "Designing the architecture of your OutSystems applications" Guide: In the section "Isolating integrations in Connectors", it states: "To correctly isolate the integration with an external service from the rest of the application, you should have two modules: a Connector to consume the external service, and a Core Service module to expose a simplified and well-defined API to the consumers." This directly supports the two-module (Connector and Wrapper/Core Service) definition in the correct answer.

2. OutSystems Official Documentation, "Validating your application architecture" Guide: Under the section "Architecture Patterns and Best Practices", the guide details the importance of wrapping integrations. It explains that a Connector module (Type: Extension or containing integrations) should be consumed by a Core module, which then exposes a public, stable API. This reinforces the structure described in option D.

3. OutSystems Training Material, "Architecture Specialist" Courseware: The course materials on Integration Architecture explicitly define the ECS pattern as having a Connector module for the raw integration and a Core Service (CS) module to provide a stable, public-facing API, abstracting the Connector's implementation details.

Scroll to Top