Which statement about Oracle Integration Cloud (OIC) is NOT valid?

An application-driven integration in Oracle Integration Cloud (OIC) is architecturally designed to have a single entry point. This means it can be initiated by exactly one trigger (source) connection that receives an inbound request. While the integration flow can subsequently invoke multiple target systems or applications (invoke connections), the fundamental pattern does not allow for more than one trigger. The statement that it can contain "one or more trigger" connections is therefore architecturally incorrect and invalid.

A. This statement is considered valid in the context of the design paradigm. Lookups are created and populated at design time as static resources, although they can be modified programmatically via the REST API.
B. This is a valid statement. The OIC connectivity agent is the specific component designed to establish a secure connection between OIC and applications residing in private, on-premises networks for hybrid integrations.
D. This is a valid statement. When the mapper is opened, it introspects the metadata (such as WSDL, XSD, or JSON schemas) of the source and target connections to automatically populate the data structure trees for mapping.

1. Correct Answer (C): Oracle Cloud Infrastructure Documentation, Using Integrations in Oracle Integration 3, "Create App Driven Orchestrations". The guide consistently describes and illustrates the creation process as starting with the selection of a single trigger connection. For example, in the section "Add a Trigger Connection," it states, "The first connection you add to an empty orchestration is the trigger connection." This implies a singular starting point.

2. Incorrect Option (A): Oracle Cloud Infrastructure Documentation, Using Integrations in Oracle Integration 3, "Manage Lookups in Integrations". This section describes creating and managing lookups (DVMs) primarily through the design-time user interface. While the REST API for Oracle Integration documentation shows endpoints for updating lookups, their primary role and definition are as design-time static resources.

3. Incorrect Option (B): Oracle Cloud Infrastructure Documentation, Using the Connectivity Agent. The documentation's home page states, "The on-premises connectivity agent enables you to create hybrid integrations and exchange messages between on-premises applications and Oracle Integration."

4. Incorrect Option (D): Oracle Cloud Infrastructure Documentation, Using Integrations in Oracle Integration 3, "Map Data in Integrations". The documentation explains, "The data structures of the source and target data are automatically populated in the mapper." This confirms the behavior described in the option.