AD0-E605 · Question #100
In a client Real-Time CDP implementation, a customer's in-store interaction data is ingested via HTTP APIs, and CRM data is ingested in batch mode four times a day. An example of what appears in…
The correct answer is B. Within minutes. Option B is correct because the in-store transaction data is ingested via streaming HTTP APIs, which means Real-Time CDP processes it near-instantaneously and continuously evaluates segment membership. When a qualifying purchase event arrives, the customer's profile is updated…
Question
In a client Real-Time CDP implementation, a customer's in-store interaction data is ingested via HTTP APIs, and CRM data is ingested in batch mode four times a day. An example of what appears in each data feed appears below:
In-Store Transaction Sample Data ----------------------------------- id date loyalty_id city store_id email_address receipt_total CRM Sample Data ----------------------------------- first_name last_name city email_address loyalty_id closest_store_id The client wishes to target CRM profiles where a set of purchases were made at a particular set of stores, in a specific city, in the last 24 hours. How soon could a customer be targeted in streaming destinations?
Options
- AWithin an hour
- BWithin minutes
- CWithin 24 hours
- DWithin 72 hours
How the community answered
(38 responses)- A11% (4)
- B76% (29)
- C8% (3)
- D5% (2)
Explanation
Option B is correct because the in-store transaction data is ingested via streaming HTTP APIs, which means Real-Time CDP processes it near-instantaneously and continuously evaluates segment membership. When a qualifying purchase event arrives, the customer's profile is updated and pushed to streaming destinations within minutes - this is the core value proposition of Real-Time CDP's streaming pipeline.
Option A (Within an hour) is wrong because streaming ingestion and streaming destinations operate far faster than an hour; minutes is the expected latency, not 60 minutes.
Option C (Within 24 hours) describes batch segmentation latency - relevant if the in-store data were batch-ingested or if a batch destination were used, but neither applies here.
Option D (Within 72 hours) is a distractor with no basis in this architecture; it would only apply to very slow batch cycles or downstream system delays unrelated to the CDP itself.
Memory tip: Match the pipeline type to the latency. Streaming in → Streaming destination = minutes. Batch in → Any destination = hours/days. The CRM batch cadence (4x/day) affects profile enrichment but doesn't block streaming segment activation triggered by the real-time transaction feed.
Topics
Community Discussion
No community discussion yet for this question.