AgentforceArchitect (Hardest)disaster-recoverymetadataoperations
Plan disaster recovery for agent metadata and active conversation state
Real World Scenario
Region outage during peak hours; agents unavailable with no documented restore or failover procedure.
Expected Answer
• Export agent metadata to git on each release
• Document RTO for agent restore and owner on-call rotation
• Failover customer messaging to status page and IVR deflection message
• Cross-region strategy per Salesforce HA documentation and contract
• Post-incident replay of queued async conversations if applicable
• DR drill semi-annual including comms plan
• Backup integration credentials and MCP endpoints inventory
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Export agent metadata to git on each release Also consider: Document RTO for agent restore and owner on-call rotation In practice: Failover customer messaging to status page and IVR deflection message Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Agent DR is customer comms plus metadata restore — practice both not only backup files.