Which activity is essential to validate permissions when testing provisioning changes?

• A. End-to-end validation
• B. Run tests in a sandbox or staging environment
• C. Reviewing logs after production
• D. Quickly deploying to production

Answer: (B)

Permissions testing for provisioning changes should be done in a sandbox or staging environment to safely validate access controls. This setup lets you mirror production conditions closely enough to exercise provisioning scripts, policy updates, and role assignments without affecting real users or data. In this space you can confirm that the intended permissions are granted and that nothing gains unintended access, while also verifying that automation and service accounts operate under the correct scopes. It provides a reproducible environment to test different scenarios, edge cases, and error paths, so you catch issues before they reach production.

Relying on production for this validation is risky because it can disrupt real users and data, and post-deployment log reviews are reactive rather than preventive. Quick production deployments skip crucial checks, increasing the chance of misconfigurations slipping through.