The four key features of Oracle Integration Cloud Enterprise (OIC) are: Application Integration: OIC excels at integrating various applications, on-premises systems, and cloud services. Enterprise Service Bus (ESB): OIC provides a central hub for managing communication between services, enabling message routing, transformation, and security enforcement. Business to Business (B2B): OIC enables secure and reliable B2B communication. Stream Analytics: OIC includes Stream Analytics, which allows real-time event analysis in Apache Sparkbased systems. Web and Mobile Application Creation is not a direct feature of OIC. OCI VPC Endpoints enhance security but are not core to OIC itself.

A Mediator is a valid SCA component in an Oracle SOA composite application. Mediators are used for routing messages, transforming data, and implementing business logic within the integration flow. They provide flexibility in manipulating messages before they reach their destination service. Incorrect Answers: BAM Adapter: While OIC offers Business Activity Monitoring (BAM), it's not an SCA component itself. BAM functionality is typically accessed through integration with external tools. B2B Agreement: B2B Agreements define message exchange protocols and security settings for Businessto- Business communication. They are not SCA components but are managed within OIC for integrations. MFT Adapter: MFT (Managed File Transfer) functionality might be used within OIC, but the adapter itself wouldn't be a core SCA component. It would likely be referenced within a composite for file transfer operations. Split-Join: This functionality is not directly represented as a separate SCA component. It's achieved through features within other SCA components like BPEL processes or Mediators for message branching and joining. Reference: https://docs.oracle.com/cd/E17904_01/doc.1111/e14773/mediator.htm

The default value for Command Notification Timeout in Oracle Cloud is 5 seconds.

A, B, and C are all true statements about OIC import/export functionality. D is false because integrations can be exported individually and imported into another OIC environment without needing to be part of a package. Packages are optional.

MFT requires creating an Oracle SOA Cloud Service instance and choosing “MFT Cluster” as the service type. Oracle MFT is available as part of the SOA Cloud Service. During provisioning, selecting "MFT Cluster" ensures that the appropriate infrastructure is set up for the MFT functionalities. Defining virtual machines: OCI manages the infrastructure for the SOA service, so you typically wouldn’t directly manage virtual machines. B2B cluster: B2B configurations might be used, but it's not mandatory during initial provisioning. ATP database: MFT does not require a separate Oracle ATP database, as it utilizes an internal database managed by OCI as part of the SOA service.