QuestionQ66

Environments

Universal Containers (UC) has implemented two full sandboxes. One, called Stage, is used for performance and regression testing, as well as production-readiness checks. The other is used primarily for user acceptance testing (UAT). Both full sandboxes were refreshed two months ago.

Currently, UC plans to begin user acceptance testing in two weeks and perform the production release in four weeks. An admin also realizes that Salesforce will have a major release in six weeks. UC must release on the current Salesforce version, but also wants to ensure that the new Salesforce release does not break anything.

What should an architect recommend?

  • A Use Sandbox Preview Guide to check if there is any necessary action needed. UC might have to prepare, refresh, and redeploy to UAT.
  • B Refresh Stage now, and do not refresh UAT. This way, Stage will be on preview and UAT will not.
  • C Visit trust.salesforce.com to figure out the preview cutoff dates, if the dates had passed, work with support to get on the preview instance.
  • D Refresh Stage from UAT now. After preview cutoff, use the upgraded one for regression test, use the non-upgraded one for user acceptance test.
Explanation

Salesforce’s Sandbox Preview Guide shows whether each sandbox is on a preview or non-preview instance and identifies the refresh action and timing needed to move it. Keeping a non-preview environment supports UAT and release validation on the current production version, while a preview sandbox can be used to regression-test the upcoming release. A sandbox’s placement must be assessed against the preview cutoff; after that cutoff, a refresh cannot be routed to a preview instance while production remains on the prior release.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!