Universal Containers would like to have a Service-Level Agreement (SLA) of 1 day for any data loss due to unintentional or malicious updates of records in Salesforce. What approach should be suggested to address this requirement?
A.
Build a daily extract job and extract data to on-premise systems for long-term backup and archival purposes.
B.
Schedule a Weekly Extract Service for key objects and extract data in XL sheets to onpremise systems.
C.
Store all data in shadow custom objects on any updates and deletes, and extract them as needed.
D.
Evaluate a third-party AppExchange app, such as OwnBackup or Spanning, etc., for backup and archival purposes.
D.
Evaluate a third-party AppExchange app, such as OwnBackup or Spanning, etc., for backup and archival purposes.
Explanation
Third-party backup tools (e.g., OwnBackup, Spanning) offer automated daily backups, point-in-time recovery, and compliance reporting—meeting the 1-day SLA. Manual exports (Options A/B) are error-prone, lack automation, and miss metadata. Shadow objects (Option C) bloat storage, increase costs, and require custom development. AppExchange solutions provide encrypted backups, granular restore (object/record-level), and audit trails without code. Daily automated backups ensure data loss is ≤24 hours old. Native Salesforce backups (weekly exports) exceed the SLA. OwnBackup also handles cross-org comparisons and sandbox seeding. For enterprise-grade backup/archival with minimal admin overhead, third-party tools are the standard solution, especially for malicious/deletion scenarios where native recovery (Recycle Bin) only retains data for 15-30 days.