Salesforce ArchitectureArchitect (Hardest)drbcpresilience
Plan disaster recovery and business continuity for Salesforce
Real World Scenario
Regulator asks for RTO/RPO documentation after competitor lost CRM access for 8 hours during regional outage.
Expected Answer
• Understand Salesforce shared responsibility: platform DR vs your config/data export
• RPO: weekly encrypted backup export plus daily incremental where required
• RTO: runbook for read-only mode, manual processes, and comms templates
• Critical integration failover: queue messages when Salesforce unavailable
• Hyperforce region awareness and instance status subscription
• Annual DR drill restoring backup to sandbox validating procedures
• Document dependencies: Einstein, Marketing Cloud, identity provider chain
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Understand Salesforce shared responsibility: platform DR vs your config/data export. RPO: weekly encrypted backup export plus daily incremental where required. Pick based on your integration pattern and team capability. Salesforce DR is not automatic failover to hot standby—architects plan degraded operations honestly. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Salesforce DR is not automatic failover to hot standby—architects plan degraded operations honestly.