What is a key feature of Edge ingestion in Adobe RT-CDP?

Question

Options

• AProcessing data in central hubs for batch activation.
• BStreaming data in real-time for immediate profile updates.
• CRestricting ingestion to structured datasets only.
• DPerforming manual identity mapping during data ingestion.

• A
  9% (6)
• B
  83% (53)
• C
  5% (3)
• D
  3% (2)

Explanation

Edge ingestion in Adobe Real-Time CDP is designed to capture and process data at the edge (close to the source), streaming it in real-time so that customer profiles are updated immediately - making B correct. Option A is wrong because edge ingestion is the opposite of centralized batch processing; it decentralizes and streams data continuously. Option C is incorrect because edge ingestion handles diverse data types including unstructured and semi-structured event data, not just structured datasets. Option D is wrong because identity mapping in RT-CDP is handled by the Identity Service automatically, not manually during ingestion.

Memory tip: Think of "Edge" as the edge of a live sports broadcast - data flows in real-time, right as events happen, updating the scoreboard (profile) instantly. If it were batch or centralized, you'd only see the score at halftime.

No community discussion yet for this question.