You are working on integration within Oracle Integration (OIC) that includes several connections to external systems. As part of your development…

Oracle Integration (OIC) provides a built-in mechanism called the Global Fault Handler for managing unhandled errors within an integration. This handler acts as a default, top-level catch block for the entire integration flow. By adding actions (such as notifications, logging, or invoking other services) to the Global Fault Handler on the integration canvas, you can define a consistent strategy to process any unexpected faults that are not caught by more specific, lower-level fault handlers (like those within a Scope action). This is the standard approach for ensuring all unexpected errors are handled correctly.

A. Oracle Integration does not have a "Try-Catch action." The equivalent is a "Scope" action, which can contain its own fault handler for a specific block of actions, not the entire integration.

B. The Rethrow Fault action is used within a fault handler to pass the fault to a higher-level handler (e.g., the Global Fault Handler), not to invoke a separate integration.

D. The Throw New Fault action is used to explicitly generate a new, custom fault within an integration, not to handle existing ones or send them to the Error Hospital.

1. Oracle Cloud Infrastructure Documentation - Using Oracle Integration 3

"Manage Errors with Fault Handlers": "Each integration includes a single global fault handler by default. The global fault handler is responsible for processing all faults that are not caught by a scope-level fault handler in the integration." This directly supports option C as the primary mechanism for handling uncaught faults.

2. Oracle Cloud Infrastructure Documentation - Using Oracle Integration 3

"Scope Action": "A scope is an action that groups a collection of other actions into a block. A scope can have its own fault handlers to catch and manage faults raised by the actions enclosed within it." This clarifies the purpose of a Scope

showing why option A is incorrect in its terminology and scope.

3. Oracle Cloud Infrastructure Documentation - Using Oracle Integration 3

"Rethrow Fault Action": "The Rethrow Fault action enables you to rethrow a fault that has been caught by a fault handler to the next-level fault handler for further processing." This confirms that Rethrow Fault propagates errors

invalidating the claim in option B.

4. Oracle Cloud Infrastructure Documentation - Using Oracle Integration 3

"Throw New Fault Action": "The Throw New Fault action enables you to throw a new fault from within an action." This shows the action is for fault generation

not handling

making option D incorrect.