Before deploying an application update broadly, best practice is to test it in an isolated environment to avoid breaking production systems. The All-in-One guide defines sandbox testing clearly: “a sandbox is a place where you can experiment without messing up the primary system,” typically a virtualized environment, and it “entails checking out new and updated applications without putting the systems and data you depend on at risk.” That directly aligns with rolling out a new application update across the organization.
Mike Meyers’ Lab Manual repeats the same concept: sandbox testing uses an isolated environment and snapshots to test changes safely before production deployment. It’s positioned as a documented business process within change-management best practices, reinforcing why it comes early—before impact spreads.
A backup/rollback plan is important too, but the question asks for the first step when applying a new update to everyone. Testing first helps identify compatibility issues, installation failures, and side effects early—so you don’t deploy a bad update at scale. Therefore, Sandbox testing (C) is correct.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit