This statement is not valid. To interact with the OIC File Server from an integration flow within the same OIC instance, the FTP Adapter must be used, not the REST Adapter. The FTP Adapter is specifically designed for file-based operations over protocols like SFTP. It is configured with the OIC File Server's host, port, and credentials to perform actions such as listing, reading, and writing files. The REST Adapter is used for invoking RESTful web services and is not suitable for SFTP file transfers.

A. This is a valid function. Administrators create users in OIC, assign them the necessary role, and configure folder permissions, allowing external SFTP clients to connect.

C. This is a valid security constraint. Administrative operations on the File Server, especially via its REST APIs, are restricted to users holding the ServiceAdministrator role.

D. This is a valid statement. The File Server feature is not enabled by default upon provisioning a new Oracle Integration instance and requires explicit activation by an administrator.

1. For Answer B (FTP Adapter Usage): Oracle Cloud Infrastructure Documentation, Using Integrations in Oracle Integration 3, "Use the Embedded SFTP Server in Oracle Integration", Section: "Use the FTP Adapter to Connect to the Embedded SFTP Server". This section explicitly states, "You can use the FTP Adapter to connect to the embedded SFTP server from an integration."

2. For Answer D (Disabled by Default): Oracle Cloud Infrastructure Documentation, Using Integrations in Oracle Integration 3, "Use the Embedded SFTP Server in Oracle Integration", Section: "Enable the Embedded SFTP Server". The first sentence reads, "The embedded SFTP server is disabled by default. A service administrator must enable it."

3. For Answer A (External Client Access): Oracle Cloud Infrastructure Documentation, Using Integrations in Oracle Integration 3, "Use the Embedded SFTP Server in Oracle Integration", Section: "Manage Users and Groups". This section details how to create users and grant them permissions to folders, which they can then access using an SFTP client.

4. For Answer C (Admin Role for REST API): Oracle Cloud Infrastructure Documentation, REST API for Oracle Integration, "File Server", Section: "Manage File Server". The documentation specifies that the "Required Role" for these API operations is ServiceAdministrator.

SOAP’s main strengths are its neutrality and use of standard Internet infrastructure.

• Because a SOAP message is just an XML document carried in a SOAP envelope, any platform or language that can parse XML can create/consume it (platform/language independence).

• The envelope plus XML body is the NORMAL, W3C-defined SOAP payload format, so two endpoints can exchange messages over any network that supports the chosen transport.

• When SOAP is bound to HTTP (the most common binding), it rides on port 80/443, a port already opened on almost every proxy and firewall, so messages are rarely blocked.

A. SOAP itself is stateless; maintaining server-side state requires additional specifications (e.g., WS-Session) or custom coding.

D. “Cleaning agent” wording is non-technical; SOAP does not remove data—it adds XML markup.

E. SOAP formatting is rigidly defined (Envelope/Header/Body) by the W3C spec; the contract (WSDL) is fixed, yielding strong coupling in message structure.

1. W3C. “SOAP Version 1.2 Part 0: Primer”, §1 & §2 (XML payload, platform neutrality).

https://www.w3.org/TR/soap12-part0/

2. Oracle Cloud Infrastructure – “Developing and Securing Web Services”, Oracle Fusion Middleware 14c, ch. 3 (“SOAP Advantages: Language and Platform Independence; Works through Firewalls”).

3. MIT OpenCourseWare, 6.170 “Software Studio”, Lecture on Web Services, slides 14-16 (SOAP over HTTP rarely blocked; XML payload).

4. P. Fremantle & H. Weerasinghe, “Web Services Framework”, IEEE Internet Computing 8(2):62-69, 2004, §“Transport Independence and Firewalls”. DOI:10.1109/MIC.2004.1273204

5. Oracle Integration Cloud Service – “Using SOAP Connections”, PDF 2023-10, p. 2 (“SOAP messages use strict XML envelope; state handled externally”).

The Stage File action's "Read File in Segments" operation is specifically designed for processing large files by creating a repeating loop structure. When an integration developer adds subsequent actions (e.g., a mapping, an adapter call) to process the data within each segment, Oracle Integration automatically encloses these actions within a Scope. This Scope acts as a container for the per-segment logic and allows for localized fault handling. Therefore, understanding that a Scope action is an integral and explicit part of this processing pattern is a critical consideration for a developer implementing this solution.

B. The configurable segment size for the "Number of records" is from 1 to 10,000, making the range of 1-200 incorrect.

C. The "Read File in Segments" operation is designed to work with file references; it is the standard and required way to pass the downloaded file to this action.

D. The "Read File in Segments" operation processes the file segments sequentially. Parallel processing would require a different pattern, such as using a "For Each" action.

1. Oracle Cloud Infrastructure Documentation, Oracle Integration 3, "Add a Stage File Action":

Reference for Correct Answer (A): In the section describing the "Read File in Segments" operation, the documentation states: "When you add actions inside the Read File in Segments loop, the actions are automatically enclosed in a scope." This confirms that a Scope is an explicit part of the design.

Reference for Incorrect Answer (B): The configuration details for the "Number of records" field specify: "The minimum value is 1 and the maximum value is 10000."

Reference for Incorrect Answer (C): The configuration wizard for the operation includes a mandatory "Specify File Reference" field, demonstrating that it is designed to process file references.

Reference for Incorrect Answer (D): The operation is described as creating a "repeating element," which implies a sequential loop. There is no mention of a parallel processing option within this specific operation. The documentation describes it as a sequential read-and-process loop.

Oracle Integration's notification service allows administrators to configure system health and service alerts to be delivered via email. The configurable alert types specifically include notifications for when the percentage of failed integration instances surpasses a defined threshold, when one or more connectivity agents become unavailable, and when security certificates are approaching their expiration date. An alert for exceeding the email quota is not a standard, configurable option within this specific system status notification framework.

A. Failed instances exceeding a specified percentage is a configurable alert type, allowing administrators to monitor integration health and receive notifications when error rates are too high.

B. One or more connectivity agents are unavailable is a critical, configurable alert, as agent availability is essential for hybrid integrations connecting to on-premises applications.

D. Certificates that are set to expire within seven days is a proactive, configurable alert that helps prevent integration failures due to expired security certificates.

1. Oracle Cloud Infrastructure Documentation - Administering Oracle Integration 3, "Configure Notifications": This official documentation page explicitly lists the types of notifications that can be configured. It details alerts for "Integration Errors" (matching option A), "Agent Status" (matching option B), and "Certificate Expiration" (matching option D). The document does not list an alert for email quota thresholds.

Reference Section: In the "Configure Notifications" section, under "Notification Types," the documentation describes the available alerts.

2. Oracle Cloud Infrastructure Documentation - Service Limits: While Oracle Integration has service limits, including for email notifications, exceeding these limits is typically managed through service usage reports and governance controls, not as a configurable system alert in the same manner as integration errors or agent status.

Reference Section: The "Service Limits" page for Oracle Integration details various quotas but does not link them to the configurable alert system described in the "Configure Notifications" documentation.

Oracle Integration Cloud (OIC) has a default payload size limit of 10 MB for synchronous, in-memory processing. To handle files larger than this limit, OIC must use a streaming approach where the file is written directly to a temporary storage area (the stage) without being fully loaded into memory.

Options A, C, and D represent valid streaming mechanisms. The REST Adapter supports receiving large files via multipart attachments (A) and downloading large files from endpoints by streaming the response to stage (D). The SOAP Adapter supports receiving large files as MTOM attachments (C), which is the standard for handling large binary data with SOAP. In all three cases, the file is made available in the OIC stage area for subsequent processing by the Stage File action.

B. Sending a large file as Base64-encoded data within the SOAP body is not viable, as the entire SOAP message, including the encoded data, is subject to the 10 MB payload limit.

E. This describes a logically flawed process. The FTP adapter connects to external FTP/sFTP servers, not the internal OIC file server (stage), to download files.

1. Oracle Integration Generation 2 Documentation, Service Limits: "The maximum size for a message payload that can be processed is 10 MB. This limit does not apply to files that are staged in Oracle Integration, which can be up to 1 GB in size." This reference establishes the core 10 MB constraint and the role of staging for larger files.

Source: Oracle Help Center, Service Limits for Oracle Integration Generation 2, Section: "Message Payload Size".

2. Oracle Integration REST Adapter Documentation (for option A): The REST Adapter can be configured as a trigger to accept multipart/form-data. "When you select Multipart Attachment, the request payload is not parsed. Instead, the request payload is directly available for you to stage and process." This confirms the streaming approach for multipart uploads.

Source: Oracle Help Center, Using the REST Adapter with Oracle Integration, Chapter: "Add the REST Adapter to an Integration", Section: "Configure the Request Page".

3. Oracle Integration SOAP Adapter Documentation (for option C): The SOAP Adapter explicitly supports MTOM for handling large attachments. "Select this checkbox [Download Attachments (MTOM)] to download attachments with an MTOM-optimized format." This is the standard mechanism for streaming large files with SOAP.

Source: Oracle Help Center, Using the SOAP Adapter with Oracle Integration, Chapter: "Add the SOAP Adapter to an Integration", Section: "Configure the Operations Page".

4. Oracle Integration REST Adapter Documentation (for option D): When invoking an external REST API, the adapter can be configured to stream the response. "Select this option [Select to Download the File] to download a file from an endpoint. The response from the endpoint is not parsed, but is written to a file in a stage location."

Source: Oracle Help Center, Using the REST Adapter with Oracle Integration, Chapter: "Add the REST Adapter to an Integration", Section: "Configure the Basic Info Page".

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.

The Monitor Integrations page, found under the Observability menu in Oracle Integration, is the central location for monitoring the state and performance of all integrations. For each listed integration, there is a "View Statistics" icon. Clicking this icon reveals a panel with aggregated instance metrics for a user-selected time period. This panel explicitly displays the total counts, minimum, maximum, average, and standard deviation for execution times, which directly corresponds to the information requested in the question.

B: The Errors page is designed for troubleshooting and managing failed instances, providing error details, not aggregated performance statistics for all instances (successful and failed).

C: The Dashboards page provides a high-level, system-wide overview of the entire Oracle Integration instance, not granular, aggregated statistics for a single, specific integration.

D: The Instances page (also known as the Tracking page) lists individual transaction instances. It is used for tracking specific runs, not for viewing aggregated statistical summaries.

1. Oracle Cloud Infrastructure Documentation - Using Oracle Integration 3: "Monitor Integrations". This document describes the functionality of the Integrations page under Observability. The section "View Integration Statistics" explicitly states: "You can view aggregated instance metrics for an integration, such as the total counts and the minimum (quickest), maximum (slowest), average (mean), and standard (largest) deviation execution times for a selected time period." This is accessed via an icon on the Integrations monitoring page.

The Oracle Integration Test page is specifically designed to invoke integrations that are exposed as web services. In addition to REST-based triggers, integrations that use a SOAP Adapter as a trigger can also be run directly from this page. The Test page provides a user interface to formulate the request payload (XML for SOAP) and send it to the integration's endpoint, allowing developers to test the integration's logic without needing an external client application.

A. Event pattern integrations: These are triggered by business events from external applications (e.g., Oracle Fusion Cloud Apps) and cannot be initiated from the Test page.

B. Schedule pattern integrations: These are triggered based on a predefined time schedule. While they can be submitted to run immediately, this is done via the "Submit Now" action, not the Test page.

D. File trigger connection-based integrations: These are initiated when a file is placed in a configured directory (e.g., on an FTP server), not by a direct invocation from the Test page.

1. Oracle Cloud Infrastructure Documentation, Using Integrations in Oracle Integration 3: In the section "Activate, Monitor, and Manage Integrations," the subsection "Test Integrations" explicitly states: "You can test integrations that are triggered by a REST Adapter or SOAP Adapter connection from the Test page. For all other types of integrations, you must invoke them from the appropriate trigger connection."

2. Oracle Cloud Infrastructure Documentation, Using Integrations in Oracle Integration Generation 2: The chapter "Manage Integrations" includes the section "Test REST Adapter and SOAP Adapter-Triggered Integrations," which details the process. It confirms that only these two trigger types are supported for testing through the designer's Test page.

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.