A travel company uses Adobe RT-CDP to deliver personalized recommendations based on real- time browsing behavior. Which profile should they leverage for low-latency personalization?

Question

Options

• AHub profile with central processing.
• BEdge profile stored locally.
• CStatic batch profile.
• DCloud-based profile for probabilistic matching.

• A
  16% (8)
• B
  71% (35)
• C
  8% (4)
• D
  4% (2)

Explanation

Edge profiles (B) are the right choice because they are stored and processed at edge nodes geographically close to the user, enabling sub-millisecond latency decisions during active browsing sessions - exactly what real-time personalization demands.

Why the distractors fail:

• A (Hub profile): The hub is Adobe's central processing layer, designed for deep batch computation and audience building - not real-time decisioning. Round-trip latency to a central hub is too slow for in-session personalization.
• C (Static batch profile): Batch profiles are built on historical data and updated on a schedule, so they can't reflect current browsing behavior within the same session.
• D (Cloud-based probabilistic profile): Probabilistic matching is a technique for identity resolution across unknown devices - it addresses who the user might be, not how fast you can serve them a recommendation.

Memory tip: Think Edge = Express lane. When a traveler is actively clicking through flight options, the edge profile is sitting at the "airport gate" ready to act - while the hub profile is back at "headquarters" still processing reports.

No community discussion yet for this question.