Org and package development models with scratch orgs
How to choose the org or package development model per project, when scratch orgs beat sandboxes as development environments, and how definition files, org shape, snapshots, durations and source tracking shape a Salesforce DX workflow.
Given a customer scenario, describe the appropriate development model (org-based vs package-based) and development environment (scratch org vs sandboxes).
~8 min read · 11 practice questions ·
What the exam expects
- Choose the org or package development model for a project from the complexity of the change, the team's size and skill, and the metadata involved, and blend them where projects differ.
- Plan a move to packages, including shared base packages and org-dependent unlocked packages.
- Choose between scratch orgs and sandboxes as development and test environments.
- Configure scratch orgs with a Dev Hub, a definition file, an org shape or a snapshot, a duration and a release.
- Know where source tracking works, how to enable it in sandboxes, and when to switch it off.
Key terms: org development model (changes released as one org-wide deployment from a manifest), package development model (versioned packages released independently, with version control as the source of truth), Dev Hub (the org that creates and manages scratch orgs), org shape (a captured edition, features, settings, limits and licenses), source tracking (keeping local source and org metadata changes in sync).
Key facts
- Detail
- Complexity of change; team size and skill; metadata worked on
- Detail
- One base package that others reference; one package per component
- Detail
- 1-30 days, default 7; can't be restored after expiry
- Detail
- Metadata types and data
- Detail
- 90 days; same Dev Hub; static
- Detail
- Developer and Developer Pro only, not Partial Copy, Full or Developer Edition; existing ones need a refresh or a per-sandbox setting
- Detail
--release previeworpreviousper scratch org
Sources for this section (7)
- Salesforce Development Modelsdeveloper.salesforce.com (opens in a new tab)
- Guide to Transitioning to Modular Package Developmenttrailhead.salesforce.com (opens in a new tab)
- Scratch Orgsdeveloper.salesforce.com (opens in a new tab)
- Create a Scratch Org Based on an Org Shapedeveloper.salesforce.com (opens in a new tab)
- Scratch Org Snapshotsdeveloper.salesforce.com (opens in a new tab)
- Enable Source Tracking in Sandboxesdeveloper.salesforce.com (opens in a new tab)
- Create Scratch Orgsdeveloper.salesforce.com (opens in a new tab)
- Why does a scratch org deployment fail when the project references fields that exist only in production?
- When should a CI job create scratch orgs with
--no-track-source? - When does an existing Developer Pro sandbox start tracking source after the production setting is enabled?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform Development Lifecycle and Deployment Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 26 lessons of the Platform Development Lifecycle and Deployment Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams