Data CloudArchitect (Hardest)drresiliencebackupcontinuity
Architect disaster recovery for Data Cloud pipelines
Real World Scenario
A failed ingestion connector deleted a week of streaming events. Marketing activations used stale segments during Black Friday.
Expected Answer
• Maintain raw event archive in S3/data lake independent of Data Cloud retention
• Document RPO/RTO per data stream: behavioral vs transactional vs consent
• Backfill procedures with idempotent keys preventing duplicate unified events
• Freeze activations automatically when freshness SLAs breach
• Run DR drills simulating connector failure before peak seasons
• Multi-region strategy if contract supports data residency failover
• Post-incident segment recomputation checklist with stakeholder communication
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Maintain raw event archive in S3/data lake independent of Data Cloud retention. Document RPO/RTO per data stream: behavioral vs transactional vs consent. Pick based on your integration pattern and team capability. Peak season readiness includes ingestion DR—not just CRM uptime. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Peak season readiness includes ingestion DR—not just CRM uptime. Architects wire freshness circuit breakers to activation paths.