Backup, Restore and Data Export Options
5 minutes
5 Questions
In Salesforce Platform Administrator II, understanding Backup, Restore, and Data Export options is essential for protecting organizational data. Salesforce does not automatically provide customer-accessible restore points for most data loss scenarios, so administrators must plan proactive backup strategies. **Data Export Service (Weekly/Monthly Export):** Found under Setup > Data Export, this native tool generates ZIP files of CSV data for standard and custom objects. Enterprise and Performance editions can schedule weekly exports; Professional and Developer editions are limited to monthly. Files include attachments, documents, and Chatter files if selected, and remain available for download for 48 hours. Exports can also be run manually (once every 7 days for weekly-enabled orgs). **Data Loader:** A client application that exports data via SOQL queries, supporting up to 5 million records. It allows selecting specific fields and filtering, and can be scheduled through command-line batch processes. It also supports insert, update, upsert, and delete, making it key for restoration from CSV backups. **Reports:** Users can export report results as CSV or Excel for lightweight, ad-hoc backups, though this is not ideal for complete org backups. **Salesforce Backup (Backup and Restore):** A paid managed package providing automated daily backups, point-in-time restore of selected records or fields, and compliance tracking. It greatly simplifies recovery compared to manual CSV restoration. **AppExchange Solutions:** Third-party tools like OwnBackup, Spanning, and Odaseva offer automated incremental backups, metadata backup, comparison, and granular restore. **Restore Considerations:** Restoring from CSV requires preserving record IDs and relationships, loading parent objects before children, mapping lookups carefully, disabling triggers/workflows temporarily, and considering the Recycle Bin (15-day retention) for recently deleted records. Metadata backups use Change Sets, Sandboxes, Salesforce CLI, or Metadata API. Administrators should document backup frequency, test restores regularly, secure exported files, and align retention with compliance requirements.
Backup, Restore and Data Export Options in Salesforce: A Complete Guide for the Advanced Administrator Exam
Introduction
Data is the most valuable asset in any Salesforce org. Backup, Restore and Data Export Options is a topic that sits inside the Advanced Data and Analytics Management domain of the Salesforce Advanced Administrator exam. Although it is a relatively small part of the exam weighting, it is a high-stakes real-world skill, and questions on it tend to be scenario-based and very answerable once you understand the tools, their limits and the trade-offs between them. This guide explains why the topic matters, what the options are, how each one works, and how to recognise the clues in exam questions that point to the correct answer.
Why Backup, Restore and Data Export Matter
Salesforce operates on a shared responsibility model. Salesforce guarantees the availability and durability of its infrastructure (servers, replication across data centres, disaster recovery for the platform as a whole), but you are responsible for protecting your own data against:
• Accidental deletion by users (a mass delete, a misconfigured Data Loader job, a deleted parent record cascading to children).
• Bad data loads that overwrite good values (for example an update that blanks a field on 50,000 accounts).
• Faulty automation such as a Flow or Apex trigger that changes records incorrectly.
• Integration errors from external systems pushing wrong data.
• Malicious actions by insiders or compromised accounts.
• Compliance and audit requirements that demand historic snapshots of data.
• Business continuity, migration and reporting outside Salesforce (data warehouses, archiving, offline analysis).
Salesforce historically offered a last-resort Data Recovery Service. It was retired in 2020, briefly reinstated as a paid, slow and expensive option, and is explicitly positioned as a last resort rather than a backup strategy. The exam expects you to know that an administrator must have a proactive backup and restore plan rather than relying on Salesforce to recover lost data.
What the Options Are: An Overview
There are several native and non-native approaches, each with a specific purpose:
1. Data Export Service (Setup > Data Export): the free, native, scheduled or on-demand full org export to CSV files.
2. Data Loader: desktop tool for Export, Export All, Insert, Update, Upsert, Delete and Hard Delete; supports command-line scheduling.
3. Report exports: quick ad-hoc extracts of a subset of data, not a true backup.
4. Salesforce Backup (Backup and Restore): Salesforce's paid, native managed package for automated daily backups and point-and-click restore.
5. AppExchange and third-party backup solutions: automated, incremental backups with metadata, comparison and granular restore (for example Own, Odaseva, Spanning, Gearset).
6. APIs (REST, SOAP, Bulk API, Metadata API): the foundation for custom or partner solutions.
7. Recycle Bin: short-term safety net for deleted records.
8. Field History Tracking and Field Audit Trail: historic field values, useful for forensics, not for bulk restore.
9. Sandboxes: a copy of production at a point in time; useful for testing restores but not a backup strategy.
10. Metadata backups: Metadata API, Salesforce CLI, VS Code, DevOps Center, Ant Migration Tool, or packages, because data exports do NOT include configuration.
How It Works: The Data Export Service
The Data Export Service is the most heavily tested option. Key facts:
• Located at Setup > Data > Data Export. Requires the Weekly Data Export user permission (included in the System Administrator profile).
• Two modes: Export Now (manual, on demand) and Schedule Export (recurring, you choose frequency, start and end dates, and preferred start time).
• Frequency depends on edition: Enterprise, Performance and Unlimited Editions can export weekly (once every 7 days). Professional and Developer Editions can export monthly (once every 29 days). Essentials is not supported.
• Export Now is subject to the same limit: you can only run it once every 7 days (weekly editions) or 29 days (monthly editions).
• Options at export time: Include images, documents and attachments; Include Salesforce Files and Salesforce CRM Content document versions; Replace carriage returns with spaces (helps when loading into tools that struggle with line breaks). You can also choose Include all data or select specific objects.
• Output: one or more zip files containing CSV files, one CSV per object. Each zip is up to 512 MB; large orgs receive multiple zip files that must be downloaded individually.
• An email notification is sent when the export is ready, and the files are available for download for 48 hours only, after which they are deleted. Admins must download and store them externally.
• Exports include standard and custom objects, but not metadata (page layouts, fields definitions, Flows, Apex, profiles) and not all system objects.
• It is a full export every time, not incremental, and there is no built-in restore: you restore by re-importing CSVs with Data Loader or Import Wizard.
• Scheduled exports can be delayed during peak times; Salesforce does not guarantee an exact run time.
How It Works: Data Loader
Data Loader is the main native restore tool and a flexible export tool:
• Export retrieves active records only; Export All also includes soft-deleted records in the Recycle Bin and archived activities.
• Handles up to 5 million records per operation, uses SOAP API by default or Bulk API for large volumes (Bulk API cannot be used with some features such as Hard Delete without the appropriate permission, and Bulk API does not support certain operations like Undelete through the UI).
• The command-line interface (CLI) on Windows allows exports to be scheduled with Windows Task Scheduler or cron-like tools, giving you daily or hourly automated exports that the Data Export Service cannot provide.
• Hard Delete bypasses the Recycle Bin and requires the Bulk API Hard Delete permission; records cannot be recovered natively.
• For restores, use Insert (new records, new IDs are generated), Update (match on Salesforce ID) or Upsert (match on Salesforce ID or an External ID field). Upsert with external IDs is the key technique for rebuilding relationships, because restored parent records receive new IDs and child lookups must be re-pointed.
• Data Loader mappings can be saved to re-use during restore.
How It Works: Salesforce Backup and Third-Party Tools
Salesforce Backup (also referred to as Backup and Restore) is a paid add-on that provides:
• Automated daily backups of selected objects, stored in Salesforce-managed storage.
• Point-in-time restore at the object or record level, including restoring deleted records and reverting field values.
• Awareness of relationships so that parent and child records can be restored together.
• Admin-friendly setup with no external infrastructure.
AppExchange solutions go further with incremental backups, metadata backups, comparison between snapshots, sandbox seeding, anonymisation and compliance features. When a question emphasises automation, frequency beyond weekly, metadata inclusion, point-in-time restore, or minimal manual effort, a paid native or AppExchange solution is usually the best answer; when it emphasises no additional cost and native, the Data Export Service or Data Loader is the answer.
How It Works: Recycle Bin, Field History and Sandboxes
• Recycle Bin: deleted records are retained for 15 days (or until capacity is exceeded). Capacity is 25 times your org's storage in MB; the oldest records are purged first when full. Records deleted by Hard Delete or emptied from the bin cannot be recovered natively. In Lightning, admins can view the org-wide Recycle Bin and restore records deleted by other users. The Recycle Bin restores records with their original IDs and relationships intact, which is why it is always the first option to check when the loss is recent.
• Field History Tracking: up to 20 fields per object, history retained for 18 months via the UI and 24 months via the API. Field Audit Trail (paid, Shield) extends retention up to 10 years and up to 60 fields per object. These show what a value was, but restoring values in bulk still requires an update via Data Loader.
• Sandboxes: a Full sandbox is a point-in-time copy of production data and metadata, refreshable every 29 days; Partial Copy every 5 days (sample of up to 10,000 records per object, 5 GB); Developer and Developer Pro every 1 day (metadata only). A sandbox can serve as a reference copy of metadata and a safe place to test a restore, but it is not a backup because it becomes stale and does not support frequent snapshots.
Restore Best Practices the Exam Expects You to Know
• Order of operations: restore parent records first (Accounts), then children (Contacts, Opportunities), then grandchildren, re-mapping lookups.
• Preserve relationships by adding External ID fields (storing the old record ID) and using Upsert, or by using a backup tool that maps old to new IDs automatically.
• Disable automation (Flows, triggers, validation rules, workflow rules, duplicate rules where appropriate) during a large restore to avoid unintended emails, task creation or failures.
• Audit fields: to preserve the original CreatedDate, CreatedById, LastModifiedDate and LastModifiedById on inserted records, enable Create Audit Fields in User Interface settings and grant the Set Audit Fields upon Record Creation permission. Auto-number values cannot be reinserted unless the field is temporarily changed to text.
• Record ownership: ownership is restored by mapping OwnerId; inactive owners cause errors unless the Update Records with Inactive Owners permission is used.
• Test first: validate the restore process in a sandbox.
• Store exports off-platform securely (encrypted, access-controlled storage) because Data Export files vanish after 48 hours and may contain sensitive data.
• Back up metadata separately with the Metadata API, Salesforce CLI, DevOps Center or source control.
Choosing the Right Tool: Quick Comparison
• Need a free, native, automated full backup: Data Export Service (weekly or monthly depending on edition).
• Need exports more often than weekly without buying a product: Data Loader CLI scheduled externally.
• Need to include soft-deleted records in an export: Data Loader Export All.
• Need a quick, filtered extract for a business user: Report export.
• Need point-in-time, record-level restore with minimal manual effort: Salesforce Backup or an AppExchange solution.
• Record deleted within the last 15 days and not hard deleted: Recycle Bin.
• Need to know what a field value was before a bad update: Field History / Field Audit Trail.
• Need a backup of configuration: Metadata API / CLI / DevOps Center, not the Data Export Service.
Exam Tips: Answering Questions on Backup, Restore and Data Export Options
1. Read for the edition. If the scenario mentions Professional or Developer Edition, scheduled exports are monthly; Enterprise, Performance and Unlimited get weekly. A question stating that an admin wants weekly exports in Professional Edition is testing whether you know this is not possible natively.
2. Spot the word native and free. Phrases such as 'without purchasing additional products', 'standard functionality' or 'out of the box' point to the Data Export Service or Data Loader. Phrases such as 'daily', 'point-in-time restore', 'minimal administrative effort' or 'include metadata' point to Salesforce Backup or an AppExchange partner.
3. Remember the limits. Export files are available for 48 hours, zip files are up to 512 MB, Export Now can run only once every 7 (or 29) days, Data Loader handles 5 million records, Recycle Bin keeps records 15 days, Field History is 18 months (10 years with Field Audit Trail).
4. Deleted records are a trap. If data was deleted recently and not hard deleted, the Recycle Bin is the simplest answer. If the deletion happened more than 15 days ago, was a Hard Delete, or the Recycle Bin was emptied, the answer must involve a backup file and Data Loader or a backup tool. If the question asks for an export that includes deleted records, the answer is Export All, not Export.
5. Relationships mean external IDs. Any scenario about restoring parent and child records together, or re-linking children to parents that were deleted and re-created, is testing External ID fields and Upsert.
6. Data is not metadata. If a question asks how to back up page layouts, Flows, validation rules or Apex, eliminate the Data Export Service and report exports immediately; choose Metadata API, Salesforce CLI, change sets to another org, DevOps Center or a sandbox refresh.
7. Automation during restore. If a scenario mentions users receiving unwanted emails or tasks being created during a data reload, the answer is to deactivate relevant Flows, workflow rules and triggers before the load.
8. Audit fields. If the requirement is to preserve original created dates or creators when reloading data, look for the Set Audit Fields upon Record Creation permission.
9. Sandboxes are not backups. An option suggesting that a Full sandbox is the backup strategy is almost always a distractor, because of the 29-day refresh interval and the fact that it is a single stale copy.
10. Report exports are not backups. They are limited in row count, lack relationships and field completeness, and are manual; treat them as a distractor unless the question is about an ad-hoc extract for a business user.
11. Shared responsibility. If an option says Salesforce automatically backs up customer data and can restore it on request at no cost, it is incorrect; Salesforce's data recovery is a last-resort, paid, slow service and the customer owns the backup responsibility.
12. Use elimination. Advanced Administrator questions typically have two obviously wrong answers and two plausible ones. Decide the key dimension the question is testing (cost, frequency, restore capability, deleted records, metadata, relationships) and pick the option that satisfies that dimension precisely.
Sample Scenario Walkthroughs
Scenario A: An Enterprise Edition admin wants an automatic, no-cost backup of all data including attachments every week, stored outside Salesforce. Answer: Schedule the Data Export Service weekly, check Include images, documents and attachments, and download the files within 48 hours to external storage.
Scenario B: A user mass-deleted 3,000 Contacts yesterday using Data Loader (standard delete). Answer: Restore them from the Recycle Bin (or Data Loader Undelete), which preserves IDs and relationships.
Scenario C: An integration overwrote the Industry field on 40,000 Accounts three weeks ago; the admin has weekly export files. Answer: Use the export CSV from before the error, map Id and Industry, and run a Data Loader Update; use Field History only to verify values.
Scenario D: A company needs hourly backups with record-level point-in-time restore and metadata comparison, and wants minimal admin effort. Answer: Implement Salesforce Backup or an AppExchange backup and restore solution; native tools cannot meet the frequency or restore requirements.
Scenario E: Accounts and their related Opportunities were deleted 2 months ago and must be restored from exports. Answer: Insert Accounts first with an External ID holding the old Account ID, then upsert Opportunities mapping the old AccountId to the External ID so lookups resolve to the new parents.
Summary
For the exam, master three things: the mechanics and limits of the Data Export Service (edition-based weekly or monthly frequency, Export Now versus Schedule, CSV zip output, 48-hour availability, attachments option, no metadata, no built-in restore), the role of Data Loader in both exporting (Export versus Export All, CLI scheduling) and restoring (Insert, Update, Upsert with External IDs, order of operations, audit fields, disabling automation), and the positioning of the other tools (Recycle Bin for the last 15 days, Field History for forensics, Salesforce Backup and AppExchange for automated point-in-time restore, Metadata API for configuration, sandboxes as test environments rather than backups). Recognise the keywords in each scenario, match them to the correct tool, and eliminate distractors that confuse data with metadata, reports with backups, or sandboxes with a backup strategy.
Data is the most valuable asset in any Salesforce org. Backup, Restore and Data Export Options is a topic that sits inside the Advanced Data and Analytics Management domain of the Salesforce Advanced Administrator exam. Although it is a relatively small part of the exam weighting, it is a high-stakes real-world skill, and questions on it tend to be scenario-based and very answerable once you understand the tools, their limits and the trade-offs between them. This guide explains why the topic matters, what the options are, how each one works, and how to recognise the clues in exam questions that point to the correct answer.
Why Backup, Restore and Data Export Matter
Salesforce operates on a shared responsibility model. Salesforce guarantees the availability and durability of its infrastructure (servers, replication across data centres, disaster recovery for the platform as a whole), but you are responsible for protecting your own data against:
• Accidental deletion by users (a mass delete, a misconfigured Data Loader job, a deleted parent record cascading to children).
• Bad data loads that overwrite good values (for example an update that blanks a field on 50,000 accounts).
• Faulty automation such as a Flow or Apex trigger that changes records incorrectly.
• Integration errors from external systems pushing wrong data.
• Malicious actions by insiders or compromised accounts.
• Compliance and audit requirements that demand historic snapshots of data.
• Business continuity, migration and reporting outside Salesforce (data warehouses, archiving, offline analysis).
Salesforce historically offered a last-resort Data Recovery Service. It was retired in 2020, briefly reinstated as a paid, slow and expensive option, and is explicitly positioned as a last resort rather than a backup strategy. The exam expects you to know that an administrator must have a proactive backup and restore plan rather than relying on Salesforce to recover lost data.
What the Options Are: An Overview
There are several native and non-native approaches, each with a specific purpose:
1. Data Export Service (Setup > Data Export): the free, native, scheduled or on-demand full org export to CSV files.
2. Data Loader: desktop tool for Export, Export All, Insert, Update, Upsert, Delete and Hard Delete; supports command-line scheduling.
3. Report exports: quick ad-hoc extracts of a subset of data, not a true backup.
4. Salesforce Backup (Backup and Restore): Salesforce's paid, native managed package for automated daily backups and point-and-click restore.
5. AppExchange and third-party backup solutions: automated, incremental backups with metadata, comparison and granular restore (for example Own, Odaseva, Spanning, Gearset).
6. APIs (REST, SOAP, Bulk API, Metadata API): the foundation for custom or partner solutions.
7. Recycle Bin: short-term safety net for deleted records.
8. Field History Tracking and Field Audit Trail: historic field values, useful for forensics, not for bulk restore.
9. Sandboxes: a copy of production at a point in time; useful for testing restores but not a backup strategy.
10. Metadata backups: Metadata API, Salesforce CLI, VS Code, DevOps Center, Ant Migration Tool, or packages, because data exports do NOT include configuration.
How It Works: The Data Export Service
The Data Export Service is the most heavily tested option. Key facts:
• Located at Setup > Data > Data Export. Requires the Weekly Data Export user permission (included in the System Administrator profile).
• Two modes: Export Now (manual, on demand) and Schedule Export (recurring, you choose frequency, start and end dates, and preferred start time).
• Frequency depends on edition: Enterprise, Performance and Unlimited Editions can export weekly (once every 7 days). Professional and Developer Editions can export monthly (once every 29 days). Essentials is not supported.
• Export Now is subject to the same limit: you can only run it once every 7 days (weekly editions) or 29 days (monthly editions).
• Options at export time: Include images, documents and attachments; Include Salesforce Files and Salesforce CRM Content document versions; Replace carriage returns with spaces (helps when loading into tools that struggle with line breaks). You can also choose Include all data or select specific objects.
• Output: one or more zip files containing CSV files, one CSV per object. Each zip is up to 512 MB; large orgs receive multiple zip files that must be downloaded individually.
• An email notification is sent when the export is ready, and the files are available for download for 48 hours only, after which they are deleted. Admins must download and store them externally.
• Exports include standard and custom objects, but not metadata (page layouts, fields definitions, Flows, Apex, profiles) and not all system objects.
• It is a full export every time, not incremental, and there is no built-in restore: you restore by re-importing CSVs with Data Loader or Import Wizard.
• Scheduled exports can be delayed during peak times; Salesforce does not guarantee an exact run time.
How It Works: Data Loader
Data Loader is the main native restore tool and a flexible export tool:
• Export retrieves active records only; Export All also includes soft-deleted records in the Recycle Bin and archived activities.
• Handles up to 5 million records per operation, uses SOAP API by default or Bulk API for large volumes (Bulk API cannot be used with some features such as Hard Delete without the appropriate permission, and Bulk API does not support certain operations like Undelete through the UI).
• The command-line interface (CLI) on Windows allows exports to be scheduled with Windows Task Scheduler or cron-like tools, giving you daily or hourly automated exports that the Data Export Service cannot provide.
• Hard Delete bypasses the Recycle Bin and requires the Bulk API Hard Delete permission; records cannot be recovered natively.
• For restores, use Insert (new records, new IDs are generated), Update (match on Salesforce ID) or Upsert (match on Salesforce ID or an External ID field). Upsert with external IDs is the key technique for rebuilding relationships, because restored parent records receive new IDs and child lookups must be re-pointed.
• Data Loader mappings can be saved to re-use during restore.
How It Works: Salesforce Backup and Third-Party Tools
Salesforce Backup (also referred to as Backup and Restore) is a paid add-on that provides:
• Automated daily backups of selected objects, stored in Salesforce-managed storage.
• Point-in-time restore at the object or record level, including restoring deleted records and reverting field values.
• Awareness of relationships so that parent and child records can be restored together.
• Admin-friendly setup with no external infrastructure.
AppExchange solutions go further with incremental backups, metadata backups, comparison between snapshots, sandbox seeding, anonymisation and compliance features. When a question emphasises automation, frequency beyond weekly, metadata inclusion, point-in-time restore, or minimal manual effort, a paid native or AppExchange solution is usually the best answer; when it emphasises no additional cost and native, the Data Export Service or Data Loader is the answer.
How It Works: Recycle Bin, Field History and Sandboxes
• Recycle Bin: deleted records are retained for 15 days (or until capacity is exceeded). Capacity is 25 times your org's storage in MB; the oldest records are purged first when full. Records deleted by Hard Delete or emptied from the bin cannot be recovered natively. In Lightning, admins can view the org-wide Recycle Bin and restore records deleted by other users. The Recycle Bin restores records with their original IDs and relationships intact, which is why it is always the first option to check when the loss is recent.
• Field History Tracking: up to 20 fields per object, history retained for 18 months via the UI and 24 months via the API. Field Audit Trail (paid, Shield) extends retention up to 10 years and up to 60 fields per object. These show what a value was, but restoring values in bulk still requires an update via Data Loader.
• Sandboxes: a Full sandbox is a point-in-time copy of production data and metadata, refreshable every 29 days; Partial Copy every 5 days (sample of up to 10,000 records per object, 5 GB); Developer and Developer Pro every 1 day (metadata only). A sandbox can serve as a reference copy of metadata and a safe place to test a restore, but it is not a backup because it becomes stale and does not support frequent snapshots.
Restore Best Practices the Exam Expects You to Know
• Order of operations: restore parent records first (Accounts), then children (Contacts, Opportunities), then grandchildren, re-mapping lookups.
• Preserve relationships by adding External ID fields (storing the old record ID) and using Upsert, or by using a backup tool that maps old to new IDs automatically.
• Disable automation (Flows, triggers, validation rules, workflow rules, duplicate rules where appropriate) during a large restore to avoid unintended emails, task creation or failures.
• Audit fields: to preserve the original CreatedDate, CreatedById, LastModifiedDate and LastModifiedById on inserted records, enable Create Audit Fields in User Interface settings and grant the Set Audit Fields upon Record Creation permission. Auto-number values cannot be reinserted unless the field is temporarily changed to text.
• Record ownership: ownership is restored by mapping OwnerId; inactive owners cause errors unless the Update Records with Inactive Owners permission is used.
• Test first: validate the restore process in a sandbox.
• Store exports off-platform securely (encrypted, access-controlled storage) because Data Export files vanish after 48 hours and may contain sensitive data.
• Back up metadata separately with the Metadata API, Salesforce CLI, DevOps Center or source control.
Choosing the Right Tool: Quick Comparison
• Need a free, native, automated full backup: Data Export Service (weekly or monthly depending on edition).
• Need exports more often than weekly without buying a product: Data Loader CLI scheduled externally.
• Need to include soft-deleted records in an export: Data Loader Export All.
• Need a quick, filtered extract for a business user: Report export.
• Need point-in-time, record-level restore with minimal manual effort: Salesforce Backup or an AppExchange solution.
• Record deleted within the last 15 days and not hard deleted: Recycle Bin.
• Need to know what a field value was before a bad update: Field History / Field Audit Trail.
• Need a backup of configuration: Metadata API / CLI / DevOps Center, not the Data Export Service.
Exam Tips: Answering Questions on Backup, Restore and Data Export Options
1. Read for the edition. If the scenario mentions Professional or Developer Edition, scheduled exports are monthly; Enterprise, Performance and Unlimited get weekly. A question stating that an admin wants weekly exports in Professional Edition is testing whether you know this is not possible natively.
2. Spot the word native and free. Phrases such as 'without purchasing additional products', 'standard functionality' or 'out of the box' point to the Data Export Service or Data Loader. Phrases such as 'daily', 'point-in-time restore', 'minimal administrative effort' or 'include metadata' point to Salesforce Backup or an AppExchange partner.
3. Remember the limits. Export files are available for 48 hours, zip files are up to 512 MB, Export Now can run only once every 7 (or 29) days, Data Loader handles 5 million records, Recycle Bin keeps records 15 days, Field History is 18 months (10 years with Field Audit Trail).
4. Deleted records are a trap. If data was deleted recently and not hard deleted, the Recycle Bin is the simplest answer. If the deletion happened more than 15 days ago, was a Hard Delete, or the Recycle Bin was emptied, the answer must involve a backup file and Data Loader or a backup tool. If the question asks for an export that includes deleted records, the answer is Export All, not Export.
5. Relationships mean external IDs. Any scenario about restoring parent and child records together, or re-linking children to parents that were deleted and re-created, is testing External ID fields and Upsert.
6. Data is not metadata. If a question asks how to back up page layouts, Flows, validation rules or Apex, eliminate the Data Export Service and report exports immediately; choose Metadata API, Salesforce CLI, change sets to another org, DevOps Center or a sandbox refresh.
7. Automation during restore. If a scenario mentions users receiving unwanted emails or tasks being created during a data reload, the answer is to deactivate relevant Flows, workflow rules and triggers before the load.
8. Audit fields. If the requirement is to preserve original created dates or creators when reloading data, look for the Set Audit Fields upon Record Creation permission.
9. Sandboxes are not backups. An option suggesting that a Full sandbox is the backup strategy is almost always a distractor, because of the 29-day refresh interval and the fact that it is a single stale copy.
10. Report exports are not backups. They are limited in row count, lack relationships and field completeness, and are manual; treat them as a distractor unless the question is about an ad-hoc extract for a business user.
11. Shared responsibility. If an option says Salesforce automatically backs up customer data and can restore it on request at no cost, it is incorrect; Salesforce's data recovery is a last-resort, paid, slow service and the customer owns the backup responsibility.
12. Use elimination. Advanced Administrator questions typically have two obviously wrong answers and two plausible ones. Decide the key dimension the question is testing (cost, frequency, restore capability, deleted records, metadata, relationships) and pick the option that satisfies that dimension precisely.
Sample Scenario Walkthroughs
Scenario A: An Enterprise Edition admin wants an automatic, no-cost backup of all data including attachments every week, stored outside Salesforce. Answer: Schedule the Data Export Service weekly, check Include images, documents and attachments, and download the files within 48 hours to external storage.
Scenario B: A user mass-deleted 3,000 Contacts yesterday using Data Loader (standard delete). Answer: Restore them from the Recycle Bin (or Data Loader Undelete), which preserves IDs and relationships.
Scenario C: An integration overwrote the Industry field on 40,000 Accounts three weeks ago; the admin has weekly export files. Answer: Use the export CSV from before the error, map Id and Industry, and run a Data Loader Update; use Field History only to verify values.
Scenario D: A company needs hourly backups with record-level point-in-time restore and metadata comparison, and wants minimal admin effort. Answer: Implement Salesforce Backup or an AppExchange backup and restore solution; native tools cannot meet the frequency or restore requirements.
Scenario E: Accounts and their related Opportunities were deleted 2 months ago and must be restored from exports. Answer: Insert Accounts first with an External ID holding the old Account ID, then upsert Opportunities mapping the old AccountId to the External ID so lookups resolve to the new parents.
Summary
For the exam, master three things: the mechanics and limits of the Data Export Service (edition-based weekly or monthly frequency, Export Now versus Schedule, CSV zip output, 48-hour availability, attachments option, no metadata, no built-in restore), the role of Data Loader in both exporting (Export versus Export All, CLI scheduling) and restoring (Insert, Update, Upsert with External IDs, order of operations, audit fields, disabling automation), and the positioning of the other tools (Recycle Bin for the last 15 days, Field History for forensics, Salesforce Backup and AppExchange for automated point-in-time restore, Metadata API for configuration, sandboxes as test environments rather than backups). Recognise the keywords in each scenario, match them to the correct tool, and eliminate distractors that confuse data with metadata, reports with backups, or sandboxes with a backup strategy.
Test mode:
Admin II - Backup, Restore and Data Export Options Example Questions
Test your knowledge of Backup, Restore and Data Export Options
Question 1
Universal Containers relies on the weekly Data Export Service for backups. After a faulty flow corrupted thousands of Opportunity and related Quote records, the restore took days. The team had to reload files with Data Loader and rebuild parent-child links by hand. Leadership now requires frequent automated backups. It also needs the ability to restore selected records, together with their child records, to a chosen point in time. Which solution best meets these requirements?
Question 2
After a bulk hard delete at Universal Containers, the administrator restores the lost Account records and their related Contact records using CSV files from last week's Data Export Service run and Data Loader. The account insert succeeds. Every contact row then fails with an invalid reference error on the Account lookup field. What explains this failure?
Question 3
At Cloud Kicks, a faulty data load overwrote the Industry and Rating values on thousands of existing Account records. A weekly Data Export Service file, generated two days before the error, holds the correct values. No records were deleted. Since the error, sales reps have made unrelated edits to other fields on many of these accounts, and those edits must be kept. What should the administrator do to recover the lost values?
Unlock Premium Access
Salesforce Certified Platform Administrator II
- Access to ALL Certifications: Study for any certification on our platform with one subscription
- 2973 Superior-grade Salesforce Certified Platform Administrator II practice questions
- Unlimited practice tests across all certifications
- Detailed explanations for every question
- Admin II: 5 full exams plus all other certification exams
- 30-Day Money-Back Guarantee: Full refund within 30 days if unsatisfied
- Risk-Free: 7-day free trial with all premium features!
More Backup, Restore and Data Export Options questions
24 questions (total)
Other Data and Analytics Management concepts
Big ObjectsBucket FieldsCross Filters and Filter LogicCustom Report TypesCustom Summary Formulas and Row-Level FormulasData Enrichment and Data Archiving StrategyData Import Wizard Versus Data LoaderData Types and Field Choice for Data QualityDynamic Dashboards and Dashboard FiltersExternal IDs and UpsertJoined ReportsMatching Rules and Duplicate RulesReporting SnapshotsSalesforce Connect and External ObjectsValidation Rules for Data Quality