Which two are NOT default start and end events in the Processes feature of Oracle Integration Cloud? (Choose two.)

BD.

Oracle Integration Cloud provides a Processes feature that allows users to model, execute and monitor business processes that involve different applications and services. When modeling a process in Oracle Integration Cloud, users can define the start and end events that mark the beginning and the end of the process flow. These events can be of different types and serve different purposes.

To answer the question, we need to identify which two options are NOT default start and end events in the Processes feature of Oracle Integration Cloud. Let's go through each option:

A. None start and end event: This option refers to the absence of a start or end event in a process flow. It means that the process has no defined starting or ending point and cannot be executed. However, this is a default option that is available in the Processes feature, as it represents the initial state of any process before events are defined.

B. Task start and end event: This option refers to the use of a task as the start and/or end event in a process flow. A task event can represent a manual or automated activity that needs to be performed before or after the process execution. This is a default option that is available in the Processes feature and is commonly used in simple processes.

C. Message start and Message end event: This option refers to the use of a message as the start and/or end event in a process flow. A message event can represent the receipt or sending of a message to or from an external application or service. This is a default option that is available in the Processes feature and is commonly used in processes that involve messaging or integration scenarios.

D. SOAP start and SOAP end event: This option refers to the use of a SOAP message as the start and/or end event in a process flow. A SOAP event can represent the receipt or sending of a SOAP message to or from an external SOAP-based web service. This is NOT a default option that is available in the Processes feature, as it requires the use of SOAP-based web services and specific configurations.

E. Folder start and None end event: This option refers to the use of a folder as the start event and the absence of an end event in a process flow. A folder event can represent the receipt or creation of a file in a folder location, which triggers the start of the process. This is NOT a default option that is available in the Processes feature, as it requires the use of file-based integration and specific configurations.

Therefore, the two options that are NOT default start and end events in the Processes feature of Oracle Integration Cloud are D. SOAP start and SOAP end event and E. Folder start and None end event.