Oracle Integration (OIC) integrations are exported as individual archive files with an .iar extension. This action is performed directly from the integrations list within the design-time environment. The concept of exporting as a "project deployment" is not the standard or required method for migrating a single integration between OIC environments. The export/import mechanism is designed to be a straightforward transfer of the integration's design-time metadata.

A. This is a valid security and portability feature. Exported .iar files intentionally exclude sensitive and environment-specific data like credentials and endpoint URLs, requiring them to be reconfigured upon import.

C. This is a valid operational dependency. An integration cannot be activated if its dependent connections are not configured, tested, and available in the target environment. The import process prompts for this configuration.

D. This is a valid automation capability. The OIC REST API provides comprehensive functions for managing the lifecycle of integrations, including updating connection properties and other configurations after an import.

1. Oracle Official Documentation, Managing Integrations in Oracle Integration 3, "Export an Integration": This section details the process: "You can export an integration to an archive file. You can then import the archive file into another Oracle Integration instance to recreate the integration." The procedure described involves selecting an integration and clicking "Export," with no mention of a "project deployment" requirement.

2. Oracle Official Documentation, Managing Integrations in Oracle Integration 3, "Import an Integration": This document explains the import process, stating, "The Connections panel is displayed for configuring the connections used by the integration... After successfully importing and configuring the integration, it must be activated." This confirms that connections must be configured before activation (validating option C).

3. Oracle Official Documentation, Using Oracle Integration 3, "Connection Properties": This documentation implicitly supports option A by describing how connection properties, including security credentials and URLs, are configured per environment and are not part of the core integration design that is exported.

4. Oracle Official Documentation, REST API for Oracle Integration, "Integrations > Update an integration": The API reference documents the PATCH and PUT methods for the /ic/api/integration/v1/integrations/{id} endpoint, which allows for programmatic modification of an integration's configuration, including its connections, thus validating option D.