A customer has a custom CRM system that holds all profiles used for marketing campaigns. The customer wants to have the data available in Adobe Campaign Classic and use it for marketing campaigns. The CRM system is relying on HTTP communication to communicate with other systems. In which two ways can the CRM system push profiles to Adobe Campaign Classic? (Choose two)

Adobe Campaign Classic provides robust API capabilities for integration with external systems. The question specifies that the source CRM system relies on HTTP communication to push data. Adobe Campaign Classic exposes two primary types of HTTP-based APIs for this purpose:
1. SOAP APIs: This is the main set of web services in Campaign Classic, allowing for comprehensive operations on the data model, including creating and updating profiles (recipients) using methods like Write and WriteCollection.
2. REST APIs: Campaign Classic also offers REST APIs, particularly for profile and service management (profileAndServicesExt API), which allow external systems to create or update profiles via standard HTTP methods like POST and PATCH. Both SOAP and REST are built on the HTTP protocol, directly satisfying the customer's requirement.

B. External Account: An External Account is a configuration within Adobe Campaign to connect outbound to other systems (e.g., a database or SFTP server), typically for data extraction or loading via a workflow. It is not an inbound endpoint for receiving data pushes.
D. SFTP: SFTP (Secure File Transfer Protocol) is a file-based protocol that operates over SSH, not HTTP. While a valid integration method for Campaign Classic, it does not meet the specific requirement of using HTTP communication.

1. Adobe Experience League, Campaign Classic v7 Documentation, "Web services (SOAP)": This section details the use of SOAP protocol calls for data-oriented APIs. It states, "The data-oriented APIs let you interact with the objects in the data model of the Adobe Campaign database... The main data-oriented services are xtk:queryDef and xtk:session." The xtk:session service includes the Write method for creating/updating entities like profiles.

2. Adobe Experience League, Campaign Classic v7 Documentation, "Transactional messaging APIs > Event description": This document describes the REST API for pushing events, which involves identifying or creating a profile. It shows a sample REST call: POST /rest/head/event. This confirms the existence and usage of REST APIs for profile interaction.

3. Adobe Experience League, Campaign Classic v7 Documentation, "Managing profiles": This page explicitly details using the REST API to create, update, or retrieve profiles. It provides the endpoint structure, such as GET /profileAndServicesExt/profile/, and describes using POST to create a new profile, directly supporting the REST option.

4. Adobe Experience League, Campaign Classic v7 Documentation, "External accounts": This documentation describes the purpose of external accounts: "External accounts let you define the parameters for connecting to external systems: server, ID, password, etc." It lists types like External Database, FTP, SFTP, and AWS S3, confirming they are for Campaign-initiated connections, not for receiving API calls.