A large retailer is moving customer loyalty data from a data warehouse to the Adobe RTCDP. The source connectors of the Adobe Experience Platform do not support this data warehouse. The data…

Question

Options

• AUse the single HTTP API request to send Multiple Messages
• BUse the Data Landing Zone API to ingest this data immediately
• CUse the Batch Ingestion API to ingest this data in bulk
• DUse Real-Time APIs to send multiple single-record requests in parallel

• A
  71% (20)
• B
  14% (4)
• C
  7% (2)
• D
  7% (2)

Explanation

Sending multiple messages in a single HTTP Streaming Ingestion API request is the most efficient approach because it leverages Adobe AEP's streaming pipeline (making data available within minutes for segmentation) while minimizing API call overhead by bundling records together rather than making one call per record.

Why the distractors are wrong:

• B (Data Landing Zone): This is a cloud-storage-based file drop zone designed for bulk file uploads, not for low-latency ingestion - data won't be ready "in a few minutes."
• C (Batch Ingestion API): Batch processing queues data for scheduled processing cycles, introducing latency of potentially hours, not minutes - too slow for near-real-time segmentation and campaigns.
• D (Real-Time APIs, multiple single-record requests in parallel): Although streaming is correct, firing one request per record is highly inefficient due to per-request overhead (auth, connection, headers). This approach wastes resources and can hit rate limits.

Memory tip: Think "stream smart" - the Streaming HTTP API supports multi-message payloads, giving you real-time speed (data in minutes) plus efficiency (one call, many records). If you see "API push + near-real-time + efficient," that combination points to a single streaming request carrying multiple messages.

No community discussion yet for this question.