1z0-1042-24 Oracle Cloud Infrastructure 2024 Application Integration Professional Questions and Answers

Read, write, list, download

Read, write, list, download, move

Read, write, list

Read, write, list, download, move, delete

Read, write

Failed instances exceeding a specified percentage.

One or more connectivity agents are unavailable.

The email quota has exceeded the threshold.

Certificates that are set to expire within seven days.

Debug-level messages require the integration’s tracing level to be set to Debug.

It always logs messages if the integration’s tracing level is set to Audit.

You can always specify to log, even when the integration’s tracing level is set to Production.

It logs messages only to the activity stream and diagnostic logs.

The View Statistics icon of the integration on the Monitor Integrations page

The Statistics icon in the integration’s activity stream on the Errors page

The Statistics icon of the integration in the Overview section of the Dashboards page

The View Statistics icon of the integration on the Instances page

Receive Business Events raised within ERP Cloud

Send Files to ERP Cloud

Extract Bulk Data from ERP Cloud

Query, Create, Update, or Delete Information

Use the REST adapter configuration wizard to define the structure of the CSV when configuring the invoke connection, then map the MTOM attachment directly.

Map the received MTOM attachment directly to the REST adapter invoke map action using the encodeReferenceToBase64 function.

Create and register a JavaScript function to convert the contents, invoke it using the JavaScript call action, then map the result to the REST adapter invoke map action.

Create an NXSD in Oracle JDeveloper to define the schema of the CSV and use it to map the transformed data to the REST adapter invoke map action.

You cannot drag and drop an XSLT flow control statement directly to a target node element.

You can drag and drop a source data element to multiple target node elements.

You cannot drag and drop a source data element to a target node element that is already mapped.

You cannot drag and drop an XPath function activity directly to a target node element.

Configure the REST Adapter to use the Basic Authentication or OAuth 2.0 security policy.

Enable Cross-Origin Resource Sharing (CORS) and set an API key in the REST Adapter configuration.

Set up an IP whitelist in the OIC instance, allowing only specific IP addresses to access the integration.

Encrypt the payload using a custom encryption algorithm and provide the decryption key to authorized clients.

Implement a scope fault handler to catch the runtime fault, and then use the Fault Return action providing mapped data for the custom fault.

Implement a scope fault handler to catch the runtime fault, then allow the global fault handler to automatically send the runtime fault to the error hospital.

Create a custom scope fault handler to catch the runtime fault, and then use the ReThrow Fault action to send the fault to the Error Hospital.

Implement the Global Fault handler to catch the runtime fault, and then use the Rethrow Fault action to send the custom fault to the client.

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.

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.

Event pattern integrations

Schedule pattern integrations

SOAP trigger connection-based integrations

File trigger connection-based integrations

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.

Any existing scheduled parameters will be automatically converted to integration properties.

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

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

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

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

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

Delete and re-create the integration to start with a clean slate.

Analyze the performance metrics of the instance, identify bottlenecks, and optimize the integration accordingly.

Reactivate the integration to clear any temporary issues that might be causing the slowdown.

Immediately increase the number of instances to handle the increased load.

Modify the parameter value in the instance’s integration properties and restart the instance.

Create a new version of the integration by modifying the parameter value, and then deploy the new scheduled integration version.

Override the parameter value when scheduling the integration instance.

Modify the parameter value in the integration code and redeploy the integration.

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

You can clone the existing integration and specify it to use the scheduled orchestration pattern.

You cannot create another integration that uses the same name.

You can create the new integration by using the same display name but with a different identifier.

Supports asynchronous REST API invocations with callback URLs

Supports JSON, XML, binary, and URL-form-encoded payloads

Consumes REST APIs protected using OAuth Client Credentials

Supports WebSocket connections for real-time communication

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.

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

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.

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.

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

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.

Increase the blocking timeout within the OIC integration settings to allow for extended time.

Change the implementation logic to invoke multiple fine-grained external API calls within a single loop.

Change the design implementation strategy to an asynchronous flow that provides a separate notification to clients when the processing is complete.

Identity certificates

Message protection certificates

Multi Domain SSL Certificate

Unified Communications Certificate

Trust Certificate

Select the Sequential Processing option and set the number of threads to the number of orders.

Select the Group By option separating the orders by their order number.

Select the Repeating Element field and map the source element that contains the orders.

Select the Parallel Processing option and set the number of threads to the number of orders.

ServiceDeveloper

ServiceAdministrator

ServiceInvoker

ServiceUser