Oracle 1z0-1042-24 Oracle Cloud Infrastructure 2024 Application Integration Professional Exam Practice Test

A client application hardcodes all URIs for resource endpoints, allowing it to navigate the API without relying on server responses.

A client application receives resource representations that include hyperlinks to related resources, enabling dynamic navigation based on the server’s responses.

A client application receives a base URI from the server and constructs all subsequent resource URIs by concatenating strings.

A client application pre-fetches all possible resource states and transitions to minimize server interactions.

Write File

Read File

Read File in Segments

Delete File

Download File

Edit

Invoke

Monitor

View

Process Automation

B2B Trading Partner Agreements

File Server

Visual Builder

Enterprise Application adapters (such as EBS, JDE, SAP, and Siebel)

SOAP clients can easily hold stateful references to remote server-side SOAP objects.

SOAP is platform independent and programming language independent.

SOAP typically leverages XML-based payloads to communicate between two client machines across any modern network.

SOAP commonly serves as a cleaning agent that removes excess data from the transmission protocol.

SOAP provides flexibility for message formatting allowing for loose coupling between a client and a server.

SOAP over HTTP is typically not blocked by firewalls and proxy servers.

You can create the new integration as a different major version of the existing one.

You can create the new integration from scratch by using the same display name and specifying a different identifier.

You can clone the existing integration and specify it to use the schedule pattern instead of the application pattern.

You can use the convert tool to change from the application pattern to the schedule pattern.

Processing of any new messages will be immediately stopped.

All existing history, monitoring, and runtime data will be lost.

You can choose to retain the event subscription, where events are resent if the integration is reactivated within six hours.

You will not be able to observe any failed instances occurring after the deactivation request.

Check the Refresh Metadata option for the ERP Cloud Connection, navigate back to your integration, then delete and recreate the map action to include the new custom objects and attributes.

Check the Refresh Metadata option for the ERP Cloud Connection, navigate back to your integration, then edit the map action to include the new custom objects and attributes.

Delete the invoke action to the ERP Cloud, re-create it, then edit the map action to include the new custom objects and attributes.

Delete the integration and recreate it to include the new custom objects and attributes in the mapaction.

Add a Try-Catch action to your integration flow and configure it to catch and handle faults.

Create a separate fault handling integration and configure your integration to invoke it when necessary using the Rethrow Fault action.

Open the Global Fault Handler page on the integration canvas and add actions to handle faults.

Use the Throw New Fault action within your integration flow to send caught faults to the OIC Error Hospital.

decodeBase64

encodeBase64

encodeReferenceToBase64

decodeBase64ToReference

Event pattern integrations

Schedule pattern integrations

SOAP trigger connection-based integrations

File trigger connection-based integrations

The data structure for the target service is always displayed on the right side in the Designer view.

In the Designer view, the Sources section contains data structures of all available data objects, which includes integration metadata, tracking variables, global variables, and integration property values.

All transformation mappings use extensible Stylesheet Language (XSL).

All Source and Target data objects are represented internally as JSON structures.

Create a connection between the two systems, then use a SQL query to access the Lookup table directly, and map the customer status codes.

Define a Lookup table containing the customer status code mappings, and then use the Invokeaction to call a web service for the transformation.

Design a custom script to perform the transformation, and then use the Lookup function within a Map action to reference the script and transform the customer status codes.

Create a Lookup table with the mappings of customer status codes, and then use the Lookup function within a Map action to reference the table and perform the transformation.

To change an integration identifier or version, you can manually edit the exported integration (IAR) file before importing it into another instance.

You cannot import an integration if it already exists with the same identifier and version.

You can export an integration either as a separate file (IAR) or bundled in a package (PAR) and it will still contain the connection resources.

You can import a package containing activated integrations.

Identity certificates

Message protection certificates

Multi Domain SSL Certificate

Unified Communications Certificate

Trust Certificate

Since the File Adapter is not supported in high-availability environments, you must use an Agent Group that uses only one installed active Agent.

You must have the OIC ServiceDeployer role or higher permissions to download and install the OIC Connectivity Agent.

Each host on which the agent is installed must be configured on separate subnets and assigned to the same OIC Agent group.

You should install the connectivity agents on the same host as the target application, and then specify different Agent group identifiers for each Agent during its installation.

You cannot have more than two Agent instances per Agent group. Attempting to include a third Agent instance in the same group during installation results in an error.

When you open the Map Editor 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.

An application pattern integration can contain one or more trigger (source) connections for requests sent to OIC and one or more invoke (target) connections for requests sent from OIC.

Using the connectivity agent, you can create hybrid integrations and exchange messages between applications in private or on-premises networks and OIC.

OIC Lookups are based on a static definition, meaning you create and populate them during design time.

After conversion, existing scheduled parameters will be automatically converted to integration properties.

You cannot convert a scheduled integration with assignments that have the fault data type.

During conversion, you must choose an existing REST Adapter trigger connection resource.

You cannot convert a scheduled integration to a REST Adapter-triggered integration with multiple verbs.

Both standard and custom HTTP headers can be defined for both the request and the response.

File attachments can be accepted as a request option for the trigger interface, but you cannot include attachments as a response to the client.

If you select a PUT or POST action (HTTP method), you must define a JSON response payload format.

Although you can define both query and template parameters, only template parameters are available for mapping in the mapper because query parameters are considered optional.

Any external SFTP client can access file server if an OIC administrator has configured specific folder access permissions for that client.

To write files to the OIC File Server from an internal OIC integration flow, a REST adapter connection resource must be used.

Access to the OIC File Server management REST APIs is limited to users with the ServiceAdministrator role.

The OIC File Server is a feature that is disabled by default in a newly provisioned OIC instance.

"FREQ=DAILY;BYDAY!=SA,SU;BYHOUR=15"

"FREQ=WEEKLY;BYDAY=MO-FR;BYHOUR=15"

"FREQ=DAILY;BYDAY=MO-FR;BYHOUR=15"

"FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR;BYHOUR=15"

Files uploaded through the Connectivity Agent can only be read with a file reference, with regard to both the Read Entire File and Read File in Segments operations.

Files uploaded through connectivity agent cannot be unzipped using a file reference.

Files uploaded through connectivity agent are not available with the zip file operation.

Files uploaded through connectivity agent are not available with the list file operation.

OIC lookups are based on a static definition, meaning you create and populate them during design time, and cannot be changed by runtime activities.

Using the connectivity agent, you can create hybrid integrations and exchange messages between applications in private or on-premises networks and OIC.

An application-driven integration can contain one or more trigger (source) connections for requests sent to OIC and one or more invoke (target) connections for requests sent from OIC.

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 source and target connections.

Check the instance logs for specific error messages and details.

Increase the number of instances to handle the error.

Immediately restart the integration instance.

Contact Oracle Support and wait for a response.

It uses XML to define the service layer document which consists of origin of the web service, headers, port types, request, and response data.

It stands for "Web Service Description Language" and is a document written in XML.

It stands for "Web Service Description Language" and is a document written in Object Notation.

It is a wrapper for a SOAP message.

It uses XML or JSON to define the service layer document which consists of origin of the web service, headers, port types, request, and response data.

Changes made while editing a Connections page cannot be recovered.

A user with the ServiceAdministrator role can unlock an integration that has unsaved changes.

A user with the ServiceAdministrator role can recover the unsaved changes.

A backup copy is created after each completed task, therefore there is no time limit to logging back in and recovering your changes.

Changes made while working inside the Map Editor cannot be recovered.

Copy and paste the entire JavaScript function code into a new JavaScript stage within the integration flow, and then map the inbound and outbound data elements in the corresponding map action.

Use the function call action within the integration flow to reference an external URL that is hosting the JavaScript library function.

Import the JavaScript library file into your OIC instance’s database schema, and then use a Local Invoke action to call the library function.

Import the JavaScript library file to the OIC Console, and then use the JavaScript action within the integration flow to reference the library function.

JavaScript functions are not allowed to make outbound calls to external services.

The JavaScript action has a timeout threshold of 60 seconds.

Active integrations using a function that has been updated must be reactivated.

Network, disk, or thread access is not supported from within a JavaScript function.

Prebuilt integrations

Auto-association of Oracle SaaS applications

User Choice of IDE for development

Public/Private Cloud portability

Data mapping recommendations

Use the Raise Fault action within your integration flow to generate custom faults and handle them accordingly.

Create a separate integration solely for the purpose of handling faults and configure your main integration to call it when necessary.

Open the Global Fault handler page on the integration canvas and add actions as needed to handle unexpected faults.

Add a Try-Catch action to your integration flow and configure it to catch and handle any faults.

Both standard and custom HTTP headers can be defined for both the request and the response.

File attachments can be accepted as a request option for the Trigger interface, but you cannot include attachments as a response to the client.

Although you can define both query and template parameters, only template parameters are available for mapping in the mapper because query parameters are considered optional.

If you select a PUT or POST action (HTTP method), you must define a JSON response payload format.