Free 1Z0-1042-25 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

The core issue is a client-side timeout caused by a long-running synchronous integration. The most effective and architecturally sound solution is to redesign the integration using an asynchronous pattern. In this model, the integration immediately accepts the client's request and returns an acknowledgment (e.g., an HTTP 202 Accepted status), freeing the client. The long-running processing, which involves updating multiple external systems, then proceeds in the background. This "fire-and-forget" approach directly resolves the client timeout issue by decoupling the client from the lengthy backend process. A separate notification mechanism, such as a callback URL, can be implemented to inform the client upon completion.

A. Increasing OIC's internal timeout does not solve the client's timeout issue and is constrained by a hard platform limit (typically 300 seconds for synchronous flows).

B. Invoking multiple fine-grained API calls within a loop would likely increase network latency and overall processing time, exacerbating the timeout problem.

1. Oracle Integration 3 Documentation

"Select an Integration Style": This document outlines the different integration patterns. It describes synchronous flows where the client is blocked waiting for a response and contrasts this with asynchronous flows. For long-running processes

the asynchronous "fire-and-forget" pattern is implicitly recommended. The documentation states for asynchronous flows

"The client is not required to wait for the process to complete."

Source: Oracle Help Center

Using Integrations in Oracle Integration 3

Chapter 2: Create Integrations

Section: "Select an Integration Style".

2. Oracle Integration 3 Documentation

"Service Limits for Oracle Integration 3": This official document specifies the hard limits of the platform. It lists the "Synchronous Request Timeout" as 300 seconds

confirming that simply increasing the timeout indefinitely (Option A) is not a viable strategy as it will eventually hit this platform constraint.

Source: Oracle Help Center

Oracle Integration 3

Section: "Service Limits for Oracle Integration 3"

Table: "Integration Limits".

3. Oracle Integration Documentation

"Best Practices for Designing Integrations": Oracle's best practices consistently advocate for using asynchronous patterns for any process that is not guaranteed to complete within a few seconds. This prevents holding client connections open and improves system scalability and reliability.

Source: Oracle Help Center

Using Integrations in Oracle Integration 3

Chapter 11: Manage Integrations

Section: "Best Practices for Designing Integrations". (This section emphasizes designing for performance and reliability

where choosing the correct pattern is a foundational principle).

The statement that is NOT valid is that the JavaScript action has a timeout threshold of 60 seconds. According to official Oracle Integration documentation, the JavaScript engine enforces specific execution limits to prevent performance degradation. The maximum execution time, or timeout threshold, for a single JavaScript action is explicitly defined as 10 minutes (600 seconds), not 60 seconds. Therefore, the consideration presented in option B is factually incorrect and not a valid limitation. The other options describe actual, documented restrictions and lifecycle requirements for using JavaScript in Oracle Integration.

A. This is a valid consideration. The JavaScript engine in Oracle Integration is sandboxed and does not permit any network access, which explicitly prohibits making outbound calls to external services.

C. This is a valid consideration. When a JavaScript library is updated, any active integration that uses it must be deactivated and then reactivated to incorporate the changes from the new library version.

D. This is a valid consideration. The Oracle Integration documentation explicitly states that for security and stability, the JavaScript execution environment does not support network, disk, or thread access.

1. Oracle Cloud Infrastructure Documentation

Using Integrations in Oracle Integration 3

"Use the JavaScript Action": This document details the capabilities and restrictions of the JavaScript action. Under the "JavaScript Action Restrictions" section

it states

"The maximum execution time for a JavaScript action is 10 minutes (600 seconds)." This directly contradicts option B.

2. Oracle Cloud Infrastructure Documentation

Using Integrations in Oracle Integration 3

"Use the JavaScript Action": The "JavaScript Action Restrictions" section also confirms options A and D by stating

"Network

disk

or thread access is not supported."

3. Oracle Cloud Infrastructure Documentation

Using Integrations in Oracle Integration 3

"Manage Libraries in Oracle Integration": This document describes the lifecycle of JavaScript libraries. It specifies the requirement for reactivation

stating

"If you update a library

you must reactivate any active integrations that use the library to have the changes take effect." This validates option C.

The Oracle Integration Cloud (OIC) File Adapter is designed to interact with files on a file server accessible through an on-premises connectivity agent. It supports a complete set of file manipulation operations. These operations include reading the content of a file, writing data to a new file, listing the files in a directory, downloading a file to Oracle Integration, moving a file between directories, and deleting a file. Option D is the only choice that comprehensively lists all six of these supported operations.

A. This option is incomplete as it omits the essential move and delete operations, which are standard capabilities of the File Adapter.

B. This option is incomplete because it fails to include the delete operation, a key function for file management and cleanup tasks.

C. This option is significantly incomplete, missing the download, move, and delete operations required for more advanced file interactions.

E. This is the most incomplete option, only listing the basic read and write operations and omitting all other file management functions.

1. Oracle Official Documentation - Using the File Adapter with Oracle Integration 3: In the "File Adapter Capabilities" section

the documentation explicitly lists the supported operations: "Read a File"

"Write a File"

"List Files"

"Download File"

"Move a File"

and "Delete a File".

Source: Oracle Help Center

"Using the File Adapter with Oracle Integration 3"

Chapter 2: Create a Connection

Section: File Adapter Capabilities.

2. Oracle Official Documentation - Using the File Adapter with Oracle Integration Gen 2: This documentation confirms the same set of capabilities for the previous generation of OIC. The "File Adapter Capabilities" section details the six operations: "Read a File"

"Write a File"

"List Files"

"Download File"

"Move a File"

and "Delete a File".

Source: Oracle Help Center

"Using the File Adapter with Oracle Integration Gen 2"

Chapter 2: Create a Connection

Section: File Adapter Capabilities.

The Wait action in an Oracle Integration schedule pattern is explicitly designed to pause the execution of an integration flow. This suspension can be configured for a specific duration (e.g., seconds, minutes, hours) or until a predefined absolute time. Its primary purpose is to introduce a deliberate delay in processing, which can be useful for scenarios like waiting for an external system to become available, batch processing, or adhering to rate limits of a target application. The flow resumes automatically after the wait condition is met.

B. This describes the functionality of a "While" action, which is used for looping based on a condition, not the "Wait" action.

C. This describes a timeout or fault-handling scenario. The Wait action's purpose is to pause execution, not to intentionally trigger an error.

D. This is the function of the schedule trigger itself, which defines when an integration instance starts, not an action performed within the running instance.

E. While a variable can be used to define the wait duration, the action's purpose is the suspension itself, not the configuration of a global variable.

1. Oracle Cloud Infrastructure Documentation. (2024). Using Integrations in Oracle Integration 3. Chapter: Create Orchestrated Integrations

Section: Add a Wait Action.

"The Wait action enables you to pause an integration flow for a specific time period. You can specify the time in seconds

minutes

hours

or days. You can also specify an exact time at which to resume the integration flow."

2. Oracle Cloud Infrastructure Documentation. (2024). Using Integrations in Oracle Integration 3. Chapter: Create Orchestrated Integrations

Section: Add a While Action.

This section describes the looping functionality

confirming it is separate from the Wait action: "The While action enables you to loop through a series of actions as long as a specified condition is met."

3. Oracle Cloud Infrastructure Documentation. (2024). Using Integrations in Oracle Integration 3. Chapter: Create Schedules.

This chapter details how to configure the initial trigger for an integration run

distinguishing it from actions within the flow: "You can create a schedule to run an integration at a specific time or on a recurring basis."

In Oracle Integration (OIC), a connection is a fundamental configuration artifact that defines the communication details for a specific application instance. Its primary purpose is to establish the link to the source and target systems that an integration will interact with. This includes endpoint URLs, security credentials, and other protocol-specific properties required to access the application's APIs or data. Connections abstract the endpoint details, allowing them to be reused across multiple integrations and managed centrally.

A. Creating custom user interfaces is the primary function of the Oracle Visual Builder capability, which is distinct from the core integration service within OIC.

B. System performance and application health are monitored through the dedicated Dashboards and Observability features within Oracle Integration, not by the connection artifacts themselves.

D. Managing user roles and access permissions is an administrative function handled through Oracle Identity and Access Management (IAM) or within the OIC settings, not through connections.

1. Oracle Cloud Infrastructure Documentation. Using Integrations in Oracle Integration 3

"About Connections".

Reference: The documentation states

"Connections define information about the instances of each configuration you are integrating... A connection is a resource that you create for each application instance that you want to integrate." This directly supports that connections specify the source and target applications.

2. Oracle Cloud Infrastructure Documentation. Get Started with Oracle Integration 3

"Oracle Integration Components"

Section: "Connections".

Reference: This guide explains

"Connections are the resources that you configure to connect to the specific instances of the applications that you want to integrate... For example

to integrate an Oracle Service Cloud (RightNow) application and a Salesforce application

you create an Oracle Service Cloud (RightNow) connection and a Salesforce connection." This confirms connections are for defining the applications being integrated.

When configuring an invoke action for the Oracle ERP Cloud Adapter in Oracle Integration and browsing by Business (REST) resources, the adapter wizard allows you to select a parent resource and its associated child resources. The official Oracle documentation does not specify a numerical upper limit on the number of child resources that can be selected. The capability is designed to accommodate the structure of the underlying ERP Cloud REST API, which can have a variable number of child resources. Therefore, you can select one or more of the available child resources, making the practical limit "unlimited" in the context of the provided options.

A. 7: This is an arbitrary number. The Oracle ERP Cloud Adapter's configuration wizard does not impose this specific limit on the selection of child resources.

B. 5: This is an arbitrary number. There is no mention of a five-child resource limit in the official Oracle documentation for the adapter.

D. 10: This is an arbitrary number. The adapter's functionality is not restricted to a maximum of ten child resources according to official sources.

1. Oracle Cloud Infrastructure Documentation. Using the Oracle ERP Cloud Adapter with Oracle Integration

"Configure the Operations Page".

Reference Details: In the section describing the configuration of an invoke (outbound) endpoint

the documentation states: "Select the checkbox for the parent resource and one or more child resources to include in the request and response." This phrasing indicates that multiple children can be selected without specifying an upper bound

supporting the "unlimited" nature of the selection.

2. Oracle Cloud Infrastructure Documentation. REST API for Oracle Fusion Cloud Financials

"Perform Actions on Resources".

Reference Details: The underlying ERP Cloud REST API documentation describes resource hierarchies (e.g.

an invoice and its lines

attachments

etc.). The number of child resources is determined by the API's design for a given parent

not by a fixed limit in the OIC adapter. The adapter's wizard is built to reflect this flexible structure.

In Oracle Integration (OIC), the standard and recommended method for using reusable custom JavaScript code is to package it as a library file (.js). This file is then imported as a resource into the OIC project. Within the integration canvas, the "JavaScript" action is used to execute code. This action can be configured to invoke specific functions defined within the imported library, promoting code reusability and maintainability across different integrations within the same project.

A. OIC is a PaaS offering; developers do not directly import files into its database schema. The "Local Invoke" action is for calling other OIC integrations, not JavaScript functions.

C. While you can write code directly in the JavaScript action, this defeats the purpose of a reusable library. The best practice for libraries is to import the file, not copy-paste code repeatedly.

D. The "Function Call" action is specifically designed to invoke serverless functions deployed on the Oracle Functions platform, not to execute JavaScript from an arbitrary external URL.

1. Oracle Official Documentation - Using Integrations in Oracle Integration 3:

Section: Call JavaScript Code in an Integration

Content: The documentation explicitly outlines the process: "You can create a JavaScript library with functions that you want to call from multiple integrations. You then register the library with Oracle Integration and call the functions from a JavaScript action in your integrations." It details the steps to add a JavaScript library to a project and then call its functions.

Reference: Oracle Help Center

Using Integrations in Oracle Integration 3

"Call JavaScript Code in an Integration".

2. Oracle Official Documentation - Using Integrations in Oracle Integration 3:

Section: Add a JavaScript Action

Content: This section describes the configuration of the JavaScript action itself. It shows how to either write inline code or

more relevantly

call a function from a registered library. This confirms that the "JavaScript" action is the correct component to use.

Reference: Oracle Help Center

Using Integrations in Oracle Integration 3

"Add a JavaScript Action".

3. Oracle Official Documentation - Using Integrations in Oracle Integration 3:

Section: Add a Function Call Action

Content: This documentation clarifies that the "Function Call" action is used to "configure a call to an Oracle Functions application." This directly refutes option D by specifying the action's true purpose.

Reference: Oracle Help Center

Using Integrations in Oracle Integration 3

"Add a Function Call Action".

The Oracle ERP Cloud adapter's capabilities are categorized as either triggers (inbound) or invokes (outbound). Options B, C, and D describe invoke actions, where the integration actively calls ERP Cloud to perform a task like sending files, extracting data, or performing CRUD operations. Option A, receiving business events, is a trigger capability. It is configured to initiate an integration when an event occurs in ERP Cloud, rather than being an action performed by the integration flow itself. The question's context implies actions an integration can perform, making the trigger the conceptual outlier among the choices.

B. Send Files to ERP Cloud: This is incorrect. The adapter's "Import Bulk Data" action is a standard feature used to send files to ERP Cloud for File-Based Data Import (FBDI) processing.

C. Extract Bulk Data from ERP Cloud: This is incorrect. The adapter provides a specific action to "Invoke a BI Publisher Report," which is the standard method for extracting bulk data from ERP Cloud.

D. Query, Create, Update, or Delete Information: This is incorrect. This represents the core functionality of the adapter, allowing it to perform CRUD operations on various business objects and services exposed by ERP Cloud.

1. Oracle Help Center

Using the Oracle ERP Cloud Adapter with Oracle Integration

"Capabilities of the Oracle ERP Cloud Adapter" section. This official documentation explicitly separates the adapter's capabilities into two distinct categories:

Inbound (trigger) direction: "You can configure the Oracle ERP Cloud Adapter to subscribe to business and custom events in Oracle ERP Cloud." (This corresponds to option A).

Outbound (invoke) direction: "You can configure the Oracle ERP Cloud Adapter to perform the following actions: Query

create

update

and delete operations... Invoke a BI Publisher (BIP) report... Upload files to Oracle Universal Content Management (UCM) and invoke a File-Based Data Import (FBDI) job..." (These correspond to options D

C

and B

respectively).

This source directly validates that A is a different type of capability (trigger) compared to B

C

and D (invokes)

which is the key distinction for answering the question.

The most fundamental and initial step in troubleshooting any failed integration instance in Oracle Integration Cloud (OIC) is to examine the instance's activity stream and logs. This provides the specific error messages, fault details, and the exact point of failure within the integration flow. This diagnostic information is essential for understanding the root cause, whether it's a data mapping issue, a connection failure, or a problem with the invoked service. Without this information, any other action would be a guess.

B. Increasing the number of instances is a scaling solution for performance issues, not a fix for a functional error that causes an instance to fail.

C. Immediately restarting the integration instance without understanding the cause is not a valid troubleshooting step and the error will likely recur.

D. Contacting Oracle Support is an escalation path, which should only be pursued after initial investigation and log analysis have been performed.

1. Oracle Cloud Infrastructure Documentation - Monitor Integrations in Oracle Integration Generation 2: "The Track Instances page enables you to monitor integration instances and view the status of your running integrations... If an instance has failed

you can view the error message from the activity stream." This document establishes the monitoring page and its activity stream as the primary tool for investigating instance failures.

Source: Oracle Help Center

Using Integrations in Oracle Integration Generation 2

Section: "Monitor Integrations".

2. Oracle Cloud Infrastructure Documentation - View the Dashboard: "The dashboard provides a quick overview of the current system status... From here

you can click a specific integration to access the Track Instances page to begin troubleshooting." This highlights that the standard workflow directs users to the instance tracking/monitoring pages to begin troubleshooting.

Source: Oracle Help Center

Using Integrations in Oracle Integration Generation 2

Section: "View the Dashboard".

3. Oracle Cloud Infrastructure Documentation - Manage Errors: "Oracle Integration provides several features for managing and troubleshooting errors... You can view details about errors on the Track Instances page." This explicitly links error management and troubleshooting to the instance tracking feature

where logs and activity streams are located.

Source: Oracle Help Center

Using Integrations in Oracle Integration Generation 2

Section: "Manage Errors".

Oracle Integration (OIC) Standard Edition provides core integration capabilities, including access to the embedded SFTP-compliant File Server for file-based integrations and Visual Builder for developing custom web and mobile applications. The Enterprise Edition includes all features of the Standard Edition, plus advanced capabilities like Process Automation and B2B. Therefore, both the File Server and Visual Builder are available in OIC Standard Edition and, by extension, also in the Enterprise Edition.

A. Process Automation: This capability for modeling, automating, and monitoring business processes is an exclusive feature of the OIC Enterprise Edition.

B. B2B Trading Partner Agreements: B2B e-commerce, which includes managing trading partner agreements, is a feature only available in the OIC Enterprise Edition.

E. Enterprise Application adapters (such as EBS, JDE, SAP, and Siebel): These specific, high-value adapters for major enterprise systems are licensed for use only with the OIC Enterprise Edition.

1. Oracle Cloud Documentation

"About Oracle Integration Editions": "Oracle Integration Standard enables you to connect your SaaS and on-premises applications... You also get Visual Builder to visually develop and host web and mobile applications." and "Oracle Integration Enterprise includes all the features of Oracle Integration Standard

plus the ability to model

monitor

and manage business processes with Process and exchange business documents with partners using B2B." This confirms Visual Builder is in Standard

while Process and B2B are Enterprise-only.

Source: Oracle Help Center

Get Started with Oracle Integration Generation 2

Section: "About Oracle Integration Editions".

2. Oracle PaaS and IaaS Universal Credits Service Descriptions: This official document details the features included in each edition.

Source: Oracle PaaS and IaaS Universal Credits Service Descriptions (E99019-121

December 2023)

Page 129

Section: "Oracle Integration". It explicitly states Standard Edition "Includes Integration... and Visual Builder" and Enterprise Edition "Includes all the features of Standard edition

plus Process Automation and B2B."

3. Oracle Cloud Documentation

"About the Embedded SFTP Server": The documentation describes the File Server as a feature of Oracle Integration

without specifying an edition

indicating its availability across the platform.

Source: Oracle Help Center

Using Integrations in Oracle Integration Generation 2

Chapter: "Manage File-Based Data"

Section: "About the Embedded SFTP Server".

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).