Deactivating an integration in Oracle Integration is a non-destructive action designed to pause its execution. This action immediately stops the integration from accepting and processing new messages. However, it does not delete or purge any existing data. All historical information, including monitoring details, tracking data, and completed runtime instances, is preserved and remains accessible on the monitoring pages. This data is subject to the standard retention policy of the Oracle Integration instance, not the activation status of a specific integration. Deactivation is a reversible state, unlike deletion.

A. Deactivating an integration immediately disables its trigger, effectively stopping the acceptance and processing of any new inbound messages or events.

C. For event-based integrations, OIC specifically provides an option to retain the event subscription for six hours, allowing missed events to be processed upon reactivation.

D. As the integration is inactive, it cannot execute or create new instances. Consequently, no new failed instances can be generated or observed after deactivation.

1. Oracle Cloud Infrastructure Documentation

Using Integrations in Oracle Integration 3

"Activate and Deactivate Integrations": This document explicitly states

"When you deactivate an integration

the trigger is disabled and no new instances are accepted... You can still monitor instances of a deactivated integration on the Track Instances page." This directly confirms that historical data is not lost (invalidating option B) and that new messages are stopped (validating option A).

2. Oracle Cloud Infrastructure Documentation

Using Integrations in Oracle Integration 3

"Manage Integrations in the Designer"

Section: "Deactivate an Integration": This section details the deactivation process for event-based integrations

stating: "If you select to retain the subscription

Oracle Integration Cloud waits six hours for you to reactivate the integration. If you reactivate within six hours

any events that occurred during the deactivation period are sent to the integration for processing." This validates option C.

Oracle Integration (OIC) provides a robust notification system to alert administrators about system health and potential issues. Administrators can configure hourly or daily email reports for specific event types. The available alert types include notifications for when the percentage of failed integration instances exceeds a defined threshold, when on-premises connectivity agents become unavailable, and when security certificates are about to expire. However, an alert for the email delivery quota being exceeded is not a configurable option within this specific notification framework. While service limits are monitored, this particular condition is not offered as a proactive email alert type.

A. Failed instances exceeding a specified percentage: This is an available alert type known as "Integration Errors," which notifies when the failure rate for an integration surpasses a configured value.

B. One or more connectivity agents are unavailable: This is a standard alert type known as "Agent Status," critical for monitoring the health of hybrid integrations.

D. Certificates that are set to expire within seven days: This is a configurable alert type known as "Certificate Expiration," which helps prevent outages due to expired certificates.

1. Oracle Cloud Infrastructure Documentation

Administering Oracle Integration Generation 2

"Configure Notifications" section.

Reference Details: In the "Notification Types" subsection

the documentation explicitly lists "Integration Errors" (matching option A)

"Agent Status" (matching option B)

and "Certificate Expiration" (matching option D) as configurable alert types for email notifications. There is no mention of an alert for an exceeded email quota. This confirms that A

B

and D are valid alert types

making C the correct answer.

For a high availability (HA) configuration of the Oracle Integration Connectivity Agent, specific prerequisites and limitations must be observed. A user must be granted the ServiceDeployer role (or a role with equivalent permissions, like ServiceAdministrator) to download the agent installer and create an agent group from the Oracle Integration console. Furthermore, the HA architecture for the connectivity agent is explicitly designed to support a maximum of two agent instances per agent group. This design provides load balancing and failover between the two nodes. Attempting to configure a third agent into the same group is not a supported configuration and will fail.

A. The File Adapter is supported in HA environments, but only one agent instance in the group can actively poll for files at a time to prevent race conditions.

C. While agents must be in the same group for HA, there is no mandatory requirement that they be installed on hosts in separate subnets.

D. For high availability, all agent instances must be configured with the same agent group identifier to function as a single logical unit for failover and load balancing.

1. Oracle Cloud Infrastructure Documentation

Using the Connectivity Agent in Oracle Integration 3

"Prerequisites for Installing the Connectivity Agent": This section explicitly states

"Ensure that you have been assigned the ServiceDeployer role. This role is required to download the connectivity agent installer and create an agent group in Oracle Integration."

2. Oracle Cloud Infrastructure Documentation

Using the Connectivity Agent in Oracle Integration 3

"High Availability Support for the Connectivity Agent": This section details the architecture and limitations

stating

"An agent group can contain a maximum of two connectivity agent instances. This provides high availability."

3. Oracle Cloud Infrastructure Documentation

Using the Connectivity Agent in Oracle Integration 3

"Adapter-Specific Behavior in a High Availability Environment": This section clarifies the behavior for specific adapters

including the File Adapter

noting that "Only one agent can be active for polling files from the configured location." This confirms the adapter is supported

but with specific operational constraints.

The creation of an agent group in Oracle Integration does not automatically create an OAuth client application. To use OAuth 2.0 for agent authentication, an administrator must manually register a confidential application in the corresponding Identity and Access Management (IAM) Identity Domain. The client ID and secret from this manually created application are then used to configure the agent's InstallerProfile.cfg file. The default authentication method for the agent uses the OIC user's credentials (Basic Authentication).

A: Creating an agent group is a mandatory prerequisite. The agent installer and its specific configuration file (InstallerProfile.cfg) are downloaded directly from the created agent group page within the OIC console.

C: The official service limits for an Oracle Integration instance explicitly state that a maximum of five agent groups can be created per instance.

D: The connectivity agent supports both Basic Authentication (using a username and password) and OAuth 2.0 token-based authentication for communicating with the Oracle Integration instance endpoints.

1. Oracle Official Documentation

"Using Integrations in Oracle Integration 3"

Chapter: "Manage Agent Groups and the Connectivity Agent"

Section: "Install the Connectivity Agent": This section states

"Before you can install the connectivity agent

you must first create an agent group." This validates that option A is a correct statement.

2. Oracle Official Documentation

"Using Integrations in Oracle Integration 3"

Chapter: "Manage Agent Groups and the Connectivity Agent"

Section: "Configure the Connectivity Agent for OAuth Authentication": This document outlines the manual procedure for configuring OAuth: "To configure the connectivity agent for OAuth authentication

you must first create a confidential application in Oracle Identity Cloud Service." This proves that the OAuth application is not created automatically with the agent group

making statement B invalid. It also confirms that OAuth is a supported authentication method

validating part of statement D.

3. Oracle Official Documentation

"Service Limits"

Section: "Integration Limits": Under the "Oracle Integration 3" or "Oracle Integration Generation 2" limits

the table for "Resource: Agent" specifies "Maximum number of agent groups per instance" as 5. This validates statement C.

4. Oracle Official Documentation

"Using Integrations in Oracle Integration 3"

Chapter: "Manage Agent Groups and the Connectivity Agent"

Section: "Download and Install the Connectivity Agent": The description of the InstallerProfile.cfg file shows parameters for oicUSER and oicPASSWORD

which are used for Basic Authentication. This

combined with the reference for OAuth configuration

confirms that both methods are supported

validating statement D.

The described scenario involves a long-running synchronous process that causes client-side timeouts. The most appropriate architectural solution is to redesign the integration using an asynchronous pattern. In this model, the integration immediately accepts the client's request and returns a 202 Accepted status, freeing the client. The time-consuming updates to external systems are then executed in the background. Upon completion, a separate mechanism, such as a callback URL or a subsequent status check, can be used to notify the client of the final outcome. This "fire-and-forget" approach is the standard best practice for decoupling clients from long-running backend processes, thereby preventing timeouts and improving system resilience.

A. Invoking multiple fine-grained API calls within a loop is likely to increase the overall processing time, which would worsen the client timeout problem, not mitigate it.

C. Increasing a timeout setting is a temporary fix, not a robust solution. The timeout is occurring on the client side, and even if OIC's timeout were increased, it promotes poor architecture by holding client connections open for extended periods.

1. Oracle Official Documentation - Develop Integrations in Oracle Integration 3: In the section "Asynchronous and One-Way Integrations

" the documentation states

"Asynchronous integrations don't block the client. When an asynchronous integration is triggered

it returns a response to the client right away with a location URL in the response header... This is useful when the task is long-running." This directly supports the strategy of changing to an asynchronous flow for long-running processes.

2. Oracle Official Documentation - Service Limits for Oracle Integration Generation 2: Under "Integration Feature Limits

" the "Inbound synchronous request timeout" is listed as 300 seconds. This highlights that synchronous processes are not designed to run indefinitely and that attempting to simply extend timeouts is not a scalable or recommended strategy

pushing developers towards asynchronous patterns for longer tasks.

3. Oracle Architecture Center - Asynchronous request-reply pattern: This architectural pattern document explains the solution for long-running operations. It states

"Use this pattern when a client needs to start a long-running operation on the backend but doesn't need to wait for the operation to complete... The client initiates a long-running operation with a call to the backend. The backend returns a 202 Accepted response immediately." This aligns perfectly with the correct answer (B).