1Z0-1042-25 practice question 10 of 15

GlobalTech Corporation uses Oracle Integration Cloud (OIC) to synchronize data between their CRM and ERP systems. They currently have a scheduled…

Full set: 99 questions
GlobalTech Corporation uses Oracle Integration Cloud (OIC) to synchronize data between their CRM and ERP systems. They currently have a scheduled integration that runs nightly at 3 AM. With the implementation of a new CRM system that supports real-time data synchronization, GlobalTech wants to update their ERP system immediately after any data changes in the CRM. To achieve this, they need to convert their scheduled integration to an app-driven integration, allowing the CRM system to trigger the integration upon data changes. When implementing this conversion, which of these considerations is NOT valid?
Answer options
A: You must choose an existing REST adapter trigger connection resource.
B: You cannot convert a scheduled integration to a REST adapter-triggered integration with multiple verbs.
C: Any existing scheduled parameters will be automatically converted to integration properties. Correct answer
D: You cannot convert a scheduled integration with assignments that have the fault data type.
Correct Answer:
C. Any existing scheduled parameters will be automatically converted to integration properties.
Explanation

When converting a scheduled integration to an app-driven integration in Oracle Integration Cloud, any existing scheduled parameters are deleted, not automatically converted. The developer is responsible for manually re-implementing the logic to handle incoming data from the new REST trigger's request payload or parameters, effectively replacing the functionality of the old scheduled parameters. The conversion wizard does not provide an automatic mechanism for this transition.

Why Incorrect

A. You must choose an existing REST adapter trigger connection resource. This is a valid requirement. The conversion wizard prompts the user to select a pre-configured REST connection that will act as the new trigger.
B. You cannot convert a scheduled integration to a REST adapter-triggered integration with multiple verbs. This is a valid limitation. The conversion process only supports creating a REST trigger with a single HTTP verb and resource URI.
D. You cannot convert a scheduled integration with assignments that have the fault data type. This is a valid, documented limitation. The conversion wizard cannot process scheduled integrations that contain an assign action using a fault data type.

References

1. Oracle Cloud Infrastructure Documentation

Using Integrations in Oracle Integration 3

"Convert a Scheduled Orchestration to an App Driven Orchestration": This official guide explicitly lists the limitations of the conversion process.

Regarding option C: "Any existing scheduled parameters are deleted. You must manually add them back as part of the request or response payload configuration of the REST Adapter Endpoint Configuration Wizard." This directly refutes the claim of automatic conversion.

Regarding option A: The documented steps show that in the "Configure Endpoint" section

the user must "select an existing REST Adapter trigger connection to use."

Regarding options B and D: The "Limitations" subsection clearly states

"You cannot convert a scheduled integration to a REST Adapter-triggered integration with multiple verbs" and "You cannot convert a scheduled integration with assignments that have the fault data type."

Scroll to Top