The statement that an application pattern integration can contain one or more trigger connections is not valid. An App Driven Orchestration in Oracle Integration (OIC) is designed to have exactly one trigger (source) connection. This single trigger acts as the entry point that initiates the integration flow. While an integration can have multiple invoke (target) connections to call various services or applications, it is fundamentally architected around a single, unique starting point.

A. This is a valid statement. The OIC Mapper automatically introspects the metadata (e.g., WSDL, XSD, JSON schema) of the configured trigger and invoke connections to populate the source and target data structure trees for mapping.

C. This is a valid statement. The OIC Connectivity Agent is specifically designed to act as a secure bridge, enabling hybrid integrations between the OIC cloud instance and applications residing in private, on-premises networks.

D. This is a valid statement. Lookups (also known as Domain Value Maps or DVMs) are design-time artifacts. You must define their structure and populate their data within the OIC console before activating the integration that uses them.

1. Oracle Official Documentation - Get Started with Oracle Integration 3, "Create an App Driven Integration": This section describes the creation of an App Driven integration, stating, "An app driven integration is triggered to run when a client sends a request to a specific endpoint." This implies a single entry point (trigger), and all visual diagrams and tutorials consistently show only one trigger initiating the flow.

2. Oracle Official Documentation - Oracle Integration, "Map Data": The documentation on the data mapper explains, "When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the trigger and invoke connections." This validates option A.

3. Oracle Official Documentation - Oracle Integration, "About the Connectivity Agent": This document states, "The on-premises connectivity agent enables you to create hybrid integrations and exchange messages between on-premises applications and Oracle Integration." This directly validates option C.

4. Oracle Official Documentation - Oracle Integration, "Manage Lookups": This guide details the process of creating and populating lookups in the design-time environment. It states, "Lookups associate values used by one application for a specific field to the values used by other applications for the same field," confirming they are design-time constructs. This validates option D.