Which practices help avoid data leakage and environment drift when testing across environments?

• A. Use production data directly in all environments.
• B. Avoid data masking entirely.
• C. Use data masking for production data in non-production environments, maintain a refresh cadence, perform environment parity checks, and run automated configuration comparisons.
• D. Make no changes to environment configurations.

Answer: (C)

The idea being tested is how to prevent data leakage while keeping testing environments aligned. Using production data directly in non-production environments can expose sensitive information and violate security controls, so masking is essential. Keeping a regular data refresh cadence ensures testers work with relevant, up-to-date data instead of stale copies, which helps the tests reflect real production behavior. Environment parity checks verify that non-production environments match production in configuration and setup, preventing drift that could hide issues. Automated configuration comparisons continuously detect any changes or drift, allowing quick corrections. Put together, masking, timely data refresh, parity checks, and automated drift detection address both the risk of data leakage and the problem of environment drift.