Describe a recommended sandbox strategy for enterprise Salesforce development.
Suggested answer
A well-structured sandbox pipeline mirrors code promotion through environments before production deployment:
Developer Sandbox: Individual developer sandbox. Metadata-only copy, refreshed quickly (1–2 hours). Used for building and unit testing. One per developer on large teams.
Developer Pro Sandbox: Larger storage (1 GB vs 200 MB). Used for integration testing between developer sandboxes and for teams that need shared feature branches.
Partial Data Sandbox: Metadata + sample data (up to 5 GB from a defined data set). Used for QA and UAT where realistic data is needed. Refresh takes hours to 1 day.
Full Sandbox: Full copy of production (metadata + all data). Used for performance testing, final UAT, and staging. Refresh takes days. Most expensive — typically 1–2 per org.
Pipeline: Developer → Developer Pro → Partial Data (QA/UAT) → Full (Staging) → Production. Promote via change sets, Salesforce CLI (sf project deploy), or CI/CD tools (Gearset, Copado). Automate deployment with scratch orgs for feature-branch isolation in DX-based projects.
Practice content for interview preparation; not an official vendor answer. Verify details against current product documentation.
Community comments (0)
No comments yet.
Sign in or create a free account to add a comment. Comments are moderated before they appear.