Data CloudIntermediatedata-qualitymonitoringquarantineops
Implement data quality monitoring and quarantine patterns
Real World Scenario
Bad email formats from a legacy CRM pollute activation exports, causing 15% bounce rates on email journeys.
Expected Answer
• Define validation rules at ingestion mapping: email regex, phone E.164, required fields
• Route failed records to quarantine DLO with error reason for steward review
• Dashboard data quality KPIs: completeness, validity, uniqueness per source
• Automated alerts when error rate exceeds baseline threshold
• Steward workflow to fix, replay, or exclude quarantined records
• Source system feedback loop notifying CRM admins of systematic issues
• SLA for quarantine resolution before next activation cycle
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Define validation rules at ingestion mapping: email regex, phone E.164, required fields Also consider: Route failed records to quarantine DLO with error reason for steward review In practice: Dashboard data quality KPIs: completeness, validity, uniqueness per source Balance speed of delivery with maintainability.
Architect Perspective
Data Cloud amplifies quality problems at activation speed—invest in quarantine upfront, not after marketing deliverability crashes.