For continuous delivery and user acceptance testing, what is a key purpose of sandboxes?

For continuous delivery and user acceptance testing, what is a key purpose of sandboxes?

• A. Provide new features directly to your customers.
• B. Test the same process you'll use to deploy and release to the production org.
• C. Develop new features or customizations.
• D. Create the package.xml file.

Answer: (B)

In continuous delivery and user acceptance testing, the sandbox’s main role is to act as a staging environment that mirrors production so you can validate the exact deployment and release steps before going live. By using a sandbox to run the full build, execute tests, and rehearse the release process, you can catch misconfigurations, data issues, and integration problems in a safe space, reducing risk when you push to production. While sandboxes can be used for development, the primary purpose here is to verify the deployment workflow and UAT readiness, not to deliver features directly to customers or to perform packaging tasks like creating a package.xml.

In continuous delivery and user acceptance testing, the sandbox’s main role is to act as a staging environment that mirrors production so you can validate the exact deployment and release steps before going live. By using a sandbox to run the full build, execute tests, and rehearse the release process, you can catch misconfigurations, data issues, and integration problems in a safe space, reducing risk when you push to production. While sandboxes can be used for development, the primary purpose here is to verify the deployment workflow and UAT readiness, not to deliver features directly to customers or to perform packaging tasks like creating a package.xml.