ARCHITECTURE-SPECIALIST-11 practice question 8 of 15

Which of the below matches the most to Library Module Pattern - Extension Pattern...

Full set: 83 questions
Answer options
A:

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:

B. 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)

C:

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

D:

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

E:

E. ... 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)

F:

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

G:

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:

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

I:

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

Correct answer
J:

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

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

The Extension Pattern, within the context of a Library Module, refers to the use of an OutSystems Extension module. This type of module is specifically designed to integrate with external resources. It acts as a wrapper to either import and use external .NET libraries (custom C# code) or to connect to an external database. When connecting to a database, it introspects the schema and creates representations of the external tables, known as Extension Entities, which can then be used within OutSystems applications as if they were native entities, albeit with certain limitations. This pattern is foundational for extending the platform's capabilities and integrating with non-standard systems.

Why Incorrect

A. This describes the Connector/Wrapper pattern for service integration, which is a higher-level pattern that might use an Extension but is not the definition of one.
B. This describes a specific event-driven synchronization pattern, a variation of the External Core Service (ECS) with a local replica.
C. This describes a "Read-Through Cache" or "Lazy Load" data synchronization strategy, not the fundamental purpose of an Extension module.
D. This describes a Facade or Abstract Core Service pattern, used to abstract multiple underlying systems behind a single interface.
E. This describes a "Partial Cache" or "Summary/Detail" data synchronization pattern, where only a subset of data is cached locally.
F. This describes the standard Core Service (CS) pattern for encapsulating business entities and logic within the OutSystems platform.
G. This describes the "Sync Wrapper" pattern, which isolates synchronization logic from the core service module that holds the cached data.
H. This describes the "External Core Service (ECS) without local replica" pattern, where data is always fetched directly from the source system.
J. This describes the "External Core Service (ECS) with local replica" pattern, where data from an external system is cached in local OutSystems entities.

References

1. OutSystems Documentation, "Extend Logic with Your Own Code": This official guide details the purpose of Extension Modules. It states, "In OutSystems, you can create Extension Modules to... Write your own C# code and make it available as actions in your applications... Integrate with external databases by mapping its tables and views to entities in your application." This directly supports the description in option I. (See the section "What is an Extension Module?").

2. OutSystems Documentation, "Architecture Canvas": The Architecture Canvas, a key concept for the exam, places Extensions in the Library layer. This layer contains reusable, non-functional modules. An Extension is a prime example, providing a reusable connection to an external database or library. (See the section "Library Modules").

3. OutSystems Training, "Designing the Architecture of Your OutSystems Applications": In the materials covering integration patterns, Extensions are presented as the low-level mechanism for connecting to external databases or wrapping custom code. The guide explains that Integration Studio is used to create these modules, which "inspect an external database and import the data structures so they can be used as entities inside of OutSystems." This aligns perfectly with the correct answer. (Refer to the "Integration Patterns" and "Module Types" sections of the courseware).

Scroll to Top