Releasing13% of the exam

Sandbox refresh plans for streams, training and hotfixes

How to place sandbox refreshes, copies and post-refresh automation on a release calendar: sharing the Full sandbox between streams, refreshing after each go-live, lead times for Quick Create, queues and the preview cutoff, training orgs per class, and the planned hotfix path.

Official exam objective
Apply map sandbox strategy to a specific Release Plan, taking into consideration multiple project streams, training requirements, staging and hotfixes.

~8 min read · 12 practice questions ·

What the exam expects

  • Map each sandbox to a job in a release plan: stream development, UAT, staging, training and hotfixes.
  • Resolve contention when several streams need the one Full sandbox, and know what a Partial Copy sandbox can't prove.
  • Schedule refreshes after each go-live and before the preview cutoff, with realistic lead times.
  • Automate post-refresh work and reconnect integrations, and plan training orgs and the hotfix path.

Key terms: refresh interval (the minimum wait between refresh requests per sandbox type), SandboxPostCopy (an Apex interface whose class runs at the end of each copy), Quick Create (the faster refresh method for Full sandboxes from Hyperforce production orgs), preview cutoff (the date by which a copy must complete to join the sandbox preview), hotfix path (the route an urgent fix takes outside the normal release).

Key facts

Refresh intervals
Detail
Developer 1 day, Developer Pro 1 day, Partial Copy 5 days, Full 29 days
Interval start
Detail
When the creation or refresh is requested
Unactivated new sandbox
Detail
Deleted after 30 days, after at least two emails
Partial Copy data
Detail
Up to 5 GB; 10,000 records per selected object (000381868); newer article: 10k parent records plus related children, or 5 GB (000387743)
Clone licence
Detail
Same type as its source
Many refreshes at once
Detail
Processed in series, not parallel
SandboxPostCopy user
Detail
Automated Process user without access to all objects
Preview request timing
Detail
At least a week before the cutoff
Sources for this section (6)
  • Why must integrations be reconfigured after every refresh?
  • When should a post-copy step be re-run by hand after activation?
  • Why should a release plan stagger sandbox refreshes instead of requesting them together?

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 (12 questions for this lesson)
  • An official source cited for every claim
  • An AI tutor that answers from the guide
  • Unlimited timed practice exams

Practice for the Platform Development Lifecycle and Deployment Architect exam