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

It is mandatory to perform validations on EDI documents for inbound translations; however, for outbound translations, it is optional.

A previously created Trading Partner Agreement is optional when configuring the inbound or outbound translation.

You can customize standard Electronic Data Interchange (EDI) documents by adding new schema constructs or by editing existing constructs.

Unified Communications Certificate

Multi Domain Certificate

Identity Certificate

Message Protection Certificate

ServiceDeveloper

ServiceAdministrator

ServiceInvoker

ServiceUser

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.

Create a custom batch call function, register the function as a Library in your OIC environment, then use the JavaScript call action to invoke the application.

Reactivate the integration and use the disable tracing and message tracking option, which will optimize performance for each invocation to the application.

Use the Append option in the Write File operation of the Stage File action within a loop to create a single batch file to be sent to the application.

Throttle the individual synchronous calls by adding a wait activity prior to each invocation to the application within the loop, then fetch a batch response after the loop.

You must create an agent group before you can run the connectivity agent installer.

Creating the agent group automatically creates an OAuth client application.

You can create up to five agent groups for each OIC instance.

The connectivity agent can use Basic Authentication or OAuth 2.0 token-based authentication when invoking OIC endpoints.

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.

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.

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.

All transformation mappings use eXtensible Stylesheet Language (XSL).

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

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

All source and target data objects are represented internally as JSON structures.

When you navigate to the mapper and select a target element, Expression Builder launches in auser-friendly mode by default.

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.

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.

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.

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.

Invoke CRUD operation on ERP Cloud REST API

Upload files to UCM

Extract Bulk Data from ERP Cloud

Enable Callback.

The exported archive file can include a map file that is largely complete in content or a map file that is empty of content.

The exported archive must be imported into an Oracle Service Bus project in JDeveloper.

Once the advanced mapping is complete, you must import the entire integration that contains the updated .xsl files.

You must export the entire integration that contains one or more .xsl files.

It is used to suspend processing within the integration flow.

It can be configured to loop through elements until a condition is met.

It is used to trigger an error after a specified duration.

It is used to schedule integration runs at specific times.

It is used to configure a global variable for delay settings.

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.

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.

7

5

Unlimited

10

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.

Read, write, list, download

Read, write, list, download, move

Read, write, list

Read, write, list, download, move, delete

Read, write

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.

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.

To create custom user interfaces for applications

To monitor system performance and application health

To specify the source and target applications that an integration connects

To manage user roles and access permissions

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.

get-value-from-lookup

lookupValue

get-content-as-string

getLookup

Exported integrations include all their dependent connection resource information except URLs and credentials.

Integration must be exported as a project deployment if you want to import them into another OIC environment.

Imported integrations cannot be immediately activated if their dependent connection resources are not already present in the target OIC environment.

Imported integrations can be reconfigured to use different connection resources by using the OIC REST API.