Four types of salesforce sandboxs Flashcards
Developer
All of your production org configurations (including custom objects, fields, etc.), but no production data. Can be refreshed—or pull in the latest configurations from production—once a day.
Recommended Uses: Good for development and testing. Because it includes all of your configurations, you can develop with the custom fields, objects, and other settings that exist in your production org, but it doesn’t include any of your real-world data.
Developer Pro
All of your production org configurations, but no production data. Can hold more data than a Developer sandbox. Can be refreshed once a day.
Recommended Uses: Good for development and quality assurance tasks, testing, and user training. Better than a Developer sandbox if you’d like to use more sample data in these processes.
Partial Copy
All of your production org configurations, plus a sample of your real-world data that you define using a sandbox template. Can be refreshed once every five days.
Recommended Uses: Good for user acceptance testing, integration testing, and training, because it contains some of your production data. Seems more like your production org than a Developer or Developer Pro sandbox.
Full
A full replica of your production org, including all configurations and all or most of the data. Can be refreshed once every 29 days.
Recommended Uses: An ideal testing environment since it is just like production. This is the only type of sandbox that supports performance testing, load testing, and staging. You probably don’t want to use Full sandboxes for development, though, because you can only refresh configurations and data every 29 days, and that refresh can take days to complete.
Where should you go in your Salesforce org to set up or refresh a sandbox org?
Settings
When your real-world data is important for training your users, what type of sandbox should you use?
Partial copy or full
How can sandboxes help you prepare for the release of changes and new features?
Testing automatically enabled features to create training plans.
Determining if you want to turn on optional features and make a plan to deploy them in production.