Which practice isolates risky code changes from production to prevent affecting users?

• A. Sandbox
• B. CI/CD
• C. Code Signing
• D. Software Assurance

Answer: (A)

Isolating risky code changes from production by testing in an isolated environment helps prevent affecting users. A sandbox creates a safe, separate space where new or experimental code can run, be stressed, and be scrutinized without touching live systems or real user data. This containment lets you observe behavior, catch crashes, security flaws, or performance regressions, and fix issues before anything reaches production. While other practices like CI/CD automate building, testing, and deploying, they don’t inherently provide this kind of isolation. Code signing verifies who produced the code and that it hasn’t been tampered with, and software assurance covers broader security and reliability processes; neither by itself isolates risky changes from users. The sandbox approach directly addresses the need to keep production safe while you validate new code.