Data CloudAdvancedstreaminglatencypersonalization
Review streaming ingestion lag causing stale personalization on website
Real World Scenario
Website personalization uses Data Cloud profile API; users see old loyalty tier for 45 minutes after upgrade because streaming connector batching misconfigured.
Expected Answer
• Verify streaming connector mapping and error queue for failed events
• Check ingestion API rate limits throttling bursts after checkout
• Measure end-to-end latency: source event → unified profile → activation API
• Alert on lag exceeding SLA threshold
• Website cache TTL must not exceed profile freshness SLA
• Priority queue for high-value events like tier change
• Load test peak events (Black Friday) before production
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Verify streaming connector mapping and error queue for failed events. Check ingestion API rate limits throttling bursts after checkout. Pick based on your integration pattern and team capability. Personalization SLA equals ingestion SLA — monitor lag as product metric not ops afterthought. Optimize for scale and operational observability.
Architect Perspective
Personalization SLA equals ingestion SLA — monitor lag as product metric not ops afterthought.