Which step is essential when testing provisioning changes before production?

• A. Validate attribute mappings
• B. Run tests in a sandbox or staging environment
• C. Ignore rollback plans
• D. Use only production accounts

Answer: (B)

When testing provisioning changes before production, the key idea is to validate how the changes will behave in a safe, real-world-like setup without touching live systems. Running tests in a sandbox or staging environment provides a replica of production where you can provision resources, apply the changes, and verify that everything works as intended, including resource creation, permissions, quotas, and how the changes interact with other systems. This kind of testing helps catch misconfigurations and integration issues and reduces the risk of downtime or data problems when you go live.

Validating attribute mappings is important for ensuring data aligns correctly, but it doesn’t by itself confirm that the full provisioning flow will operate smoothly in production. Using only production accounts is risky because it can disrupt actual users and services. And skipping rollback plans leaves you exposed to trouble if something goes wrong; you should have and practice rollback procedures. So, testing in a sandbox or staging environment is the essential step to validate provisioning changes before production.