A QA engineer says: "We replaced the production database dump with a sanitised copy for use in the staging environment."
What does "sanitised copy" mean in test data management?
Sanitised copy — a key TDM concept:
Technique
How it sanitises
Preserves format?
Data masking
Replaces real values with realistic fakes (e.g., "John Smith" → "Jane Doe")
Yes
Pseudonymisation
Replaces identifiers with tokens; reversible with key
Yes
Anonymisation
Irreversibly removes identifiers
Partially
Key vocabulary: sanitised copy, PII scrubbing, data masking, test data management (TDM), GDPR-compliant test environment.
2 / 14
A data engineer explains: "We use production data masking rather than fully synthetic data for our test environments."
What is the primary difference between production data masking and synthetic test data generation?
Masking vs. Synthetic test data:
Approach
Source
Edge cases
Privacy
Data masking
Real production data (transformed)
Preserved
Depends on masking quality
Synthetic test data
Generated from scratch (rules/ML)
Must be explicitly designed
No real data exposure
Key vocabulary: static data masking, dynamic data masking, data subsetting, format-preserving encryption, test data provisioning.
3 / 14
A database architect raises a concern: "When we generate synthetic test data for the orders table, we need to maintain referential integrity with the customers and products tables."
What does referential integrity mean in test environments?
Referential integrity in test data generation:
Concept
Example
Foreign key constraint
orders.customer_id must exist in customers.id
Cascade generation
Generate parent records before child records
Orphan records
Child records with no matching parent — a referential integrity violation
Tools and vocabulary: synthetic data generator, entity relationship diagram (ERD), parent-child generation order, constraint-aware generation, Faker, Mimesis.
4 / 14
A compliance officer asks whether the team's staging environment is GDPR-compliant given that it uses copies of production customer data.
Which approach to test data management best addresses GDPR compliance concerns?
GDPR and test environments:
GDPR principle
Implication for test data
Data minimisation
Only process personal data that is necessary — test environments rarely need real PII
Purpose limitation
Data collected for one purpose (e.g., transactions) should not be repurposed for testing
Storage limitation
Personal data should not be retained in test systems beyond what is necessary
Key vocabulary: GDPR-compliant test environment, data minimisation, purpose limitation, personal data, pseudonymisation, right to erasure.
5 / 14
A DevOps team is setting up a test data management (TDM) pipeline. A developer asks: "What is the difference between static data masking and dynamic data masking?"
Which answer correctly distinguishes the two?
Static vs. Dynamic Data Masking:
Type
When masking is applied
Original data
Use case
Static (SDM)
At copy/extract time; data at rest
Not affected
Test/dev environments
Dynamic (DDM)
At query time; real time
Unchanged in DB
Production access control
Key vocabulary: static data masking, dynamic data masking, data obfuscation, masking policy, column-level security, role-based data access.
6 / 14
John from the security team commented on your PR: 'I'm seeing a lot of Personally Identifiable Information (PII) in these test data sets. We need to ensure we're using appropriate masking techniques – specifically, redaction or pseudonymization – before deploying any changes to staging.' What does 'redaction' refer to in the context of test data management?
Redaction is a specific masking technique where sensitive information, like names or addresses, are completely removed from the test data. This differs from pseudonymization (option A), which retains some identifiers, and encryption (option C), which focuses on security rather than data transformation. It's crucial to understand these distinctions when managing test environments to avoid compliance issues.
7 / 14
Sarah, a data analyst, sent this Slack message: 'I've created a new dataset for the user authentication tests. It uses fully synthetic customer records - we haven't touched any real production data. This is faster than masking but could introduce biases.' What is a potential drawback of using *fully synthetic* test data?
While synthetic data offers speed and isolation, a key limitation is the potential for bias. If the generation process doesn't accurately mirror the statistical properties and correlations found in production data, the test results may not be representative of real-world scenarios. This can lead to inaccurate conclusions and flawed development decisions.
8 / 14
David from the performance team flagged a slow query during testing. He suggested 'reducing the volume of test data' to improve response times. In the context of Test Data Management, what does 'reducing the volume of test data' typically refer to?
'Reducing the volume of test data' in this scenario primarily refers to techniques like data masking or anonymization. These methods remove sensitive information from the dataset, preventing performance bottlenecks caused by large datasets containing PII. Option A describes generating *more* data, which would likely exacerbate the problem, and options C & D are unrelated to the core concept of controlling test data size.
9 / 14
Maria, a QA engineer, is reviewing a PR that introduces new test data. She notes: 'We're using differential backups to ensure our staging environment mirrors production as closely as possible.' How does the use of 'differential backups' relate to Test Data Management?
Differential backups are incremental copies that capture *only* the changes made since the last full backup. This makes them ideal for creating a staging environment that closely mirrors production – essential for accurate testing. Synthetic data generation (Option A) is a different approach. Option C describes encryption, and option D is incorrect.
10 / 14
During a code review, Alex from the security team remarks: 'I'm noticing that our test data includes full email addresses. We need to implement stricter anonymization – specifically, using techniques like pseudonymization or tokenization to replace them.' What does 'tokenization' refer to in the context of test data management?
Tokenization is a key technique where sensitive data like email addresses are replaced with random, unique identifiers (tokens). This preserves the functionality of the data while preventing direct access to real personal information. The misconception here might be that it's simply hashing – which only provides one-way encryption – or scrubbing, which deals with removing PII from a database, but tokenization focuses on substitution.
11 / 14
In a Slack channel discussing test data strategies, Ben (a DevOps engineer) writes: 'To avoid potential issues with GDPR, we're using a process called 'data subsetting.' It involves creating smaller, representative samples of our production data for testing purposes. What is 'data subsetting' primarily used to achieve?
Data subsetting is about creating reduced copies of production data. This is crucial for GDPR compliance because you're only dealing with a smaller amount of sensitive information and can more easily demonstrate that the test environment isn't a full replica of production. The other options present incorrect interpretations – complete anonymization is difficult, synthetic data generation is different, and automatic PII removal isn't the primary goal.
12 / 14
During a standup meeting, Chloe (a test automation engineer) explains: 'We're using a data virtualization layer to manage our test data. It allows us to create logical views of the data without physically copying it.' What is the benefit of using a data virtualization layer in Test Data Management?
Data virtualization layers provide an abstraction layer that allows you to interact with data sources (like your databases) without needing to physically copy or move them. This is highly beneficial in TDM because it enables flexibility and avoids the logistical challenges of managing multiple copies of production data. The incorrect options focus on storage costs, complete copying, or automated updates – which are separate concerns.
13 / 14
A project manager asks: 'To ensure our staging environment accurately reflects production, we're using a strategy called 'golden data.' What does the term 'golden data' refer to in the context of test data management?
'Golden data' in TDM represents the most reliable and accurate version of your production data – typically a master copy – used to populate test environments. This ensures consistency and reduces the risk of testing on outdated or inaccurate data. Misconceptions might include it being just the latest version, synthetic data, or an automated discrepancy correction tool.
14 / 14
You receive a code review comment from Liam (a senior developer): 'We're using feature flags to control which users see the new payment functionality in our test environment. This allows us to isolate testing and avoid impacting real customers.' What is the primary purpose of using feature flags in relation to Test Data Management?
Feature flags enable developers to selectively enable or disable functionality in a running application – in this case, the payment feature. This is crucial for TDM because it allows you to isolate testing on a subset of data without impacting real users and facilitates controlled experimentation with different test datasets.
What will I learn from the "Test Data Management Vocabulary Exercises" exercise?
Practice English vocabulary for test data management: production data masking, synthetic test data, referential integrity in test environments, and sanitised copies.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 14 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Synthetic Data Vocabulary exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss synthetic data vocabulary topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 14 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Synthetic Data Vocabulary exercises?
See the full Synthetic Data Vocabulary exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.