The Connector Pattern, a type of Library Module, serves as a dedicated wrapper for integrating with an external system. Its primary responsibility is to encapsulate all technical aspects of the connection, such as API methods (e.g., REST/SOAP), data structures, and authentication logic. This pattern isolates the complexities of the external system, translating its data and operations into a format that can be easily consumed within the OutSystems platform. This is achieved by either consuming a service definition or using Integration Studio to inspect an external database or library, thereby creating a clear and reusable integration point.

A. This describes a synchronization pattern with notifications (webhooks), which is a specific implementation built on top of a connector, not the connector pattern itself.

B. This describes a "no local cache" data access strategy, focusing on the runtime behavior of an integration rather than the structural pattern of the connector module.

C. This describes the "Sync Wrapper" pattern, where synchronization logic is isolated from the core service, which is a pattern related to data replication.

D. This describes the "Hybrid" or "Partial Cache" data synchronization pattern, where only a subset of data is stored locally.

E. This describes the "Core Service" or "Entity Core Service" (ECS) pattern, which is about encapsulating business entities and logic, not external system integration.

G. This describes an "Aggregation" or "Federation" pattern, which abstracts multiple data sources, a more complex pattern than a basic connector.

H. This describes the "Lazy Load" or "Read-Through Cache" data synchronization pattern, where data is cached on demand.

I. This describes the "Integration Wrapper" pattern, which involves two modules (a Connector and a Core Service Wrapper). The question asks specifically for the Connector pattern.

J. This describes the "Local Replica" or "Full Cache" data synchronization pattern, where external data is fully replicated in local entities.

1. OutSystems Official Documentation

"Designing the architecture of your OutSystems applications

" Section: Core Modules.

This section defines a Connector as a specific type of Library module that "wraps an external system

like a database or a web service. It contains all the necessary elements to connect to the external system

such as Integration logic

data Structures

and authentication." This directly supports the description in option F.

2. OutSystems Official Documentation

"Integration with External Systems

" Section: Isolate integration logic in Connectors.

This guide states

"Create a dedicated module

a Connector

to isolate the communication details. This module contains the consumed services

structures

and logic to handle authentication and logging." This reinforces that a connector's role is to encapsulate and wrap the technical integration details

as described in option F.