What should a test data refresh process define?

• A. Clear rules for when and how test data is refreshed, who handles it, and how privacy is protected.
• B. Refresh data only once at project start.
• C. Use production data without masking.
• D. Never refresh test data.

Answer: (A)

A test data refresh process should define how test data is updated in a controlled, repeatable way, including when to refresh, who is responsible, and how privacy and security are protected. This ensures the test environment stays realistic and current without exposing sensitive information. A good refresh plan specifies scheduling or triggers for refresh, the data sources and scope (full dataset or a representative subset), and the roles and responsibilities of the people or teams involved. It also outlines data masking or anonymization procedures, access controls, and auditing so production data cannot be exposed in non-production environments. Additionally, it covers validation steps to verify the refreshed data is usable and accurate, rollback procedures if something goes wrong, and retention/cleanup policies. Because it explicitly addresses timing, responsibility, and privacy safeguards, it properly guides safe, effective testing. The other options fail to maintain data currency, risk leaking production data, or ignore data refresh needs, which undermines both test relevance and security.