Practise vocabulary for implementing data deletion: right to erasure, deletion cascades, audit trails, and data retention policies.
0 / 10 completed
1 / 10
GDPR Article 17 grants individuals the ___ — the right to have their personal data erased under certain conditions.
The Right to Erasure (GDPR Article 17) allows individuals to request deletion of their personal data. Organisations must delete it without undue delay (typically 30 days) unless a legal basis for retention exists.
2 / 10
A ___ deletion ensures that when a user record is deleted, all related records in linked tables are also deleted automatically.
Cascade deletion propagates deletions through related tables via foreign key constraints (ON DELETE CASCADE). In privacy, this must cover all tables holding the user's data — which requires comprehensive data mapping.
3 / 10
___ deletion marks a record as deleted without physically removing it, keeping the data for audit or legal hold purposes.
Soft deletion (logical deletion) sets a 'deleted_at' timestamp or 'is_deleted' flag without removing the row. Physical data removal (hard deletion) happens in a separate, scheduled job — often necessary for compliance with retention schedules.
4 / 10
A data ___ policy defines how long each category of data may be retained before it must be deleted or anonymised.
A data retention policy specifies retention periods per data category (e.g., financial records: 7 years, marketing cookies: 1 year, IP addresses: 30 days). Automated deletion jobs enforce the policy at scale.
5 / 10
After completing a deletion request, a privacy engineer should generate a ___ confirming which data was deleted, from which systems, and when.
A deletion audit log (or deletion certificate) documents the erasure: timestamp, systems affected, data categories deleted, and the requestor's ID. This provides evidence of compliance in case of regulatory inquiry.
6 / 10
During a code review of the user profile deletion pipeline, Sarah from Legal flags an issue. 'We need to ensure compliance with GDPR Article 17,' she states. 'This requires us to implement a complete deletion – not just marking records as inactive.' What does Sarah likely mean in this context?
Sarah is referring to a complete deletion, which aligns with GDPR Article 17's right to erasure. A 'complete' deletion goes beyond simply disabling a record; it necessitates removing all associated data across linked systems – this is crucial for genuinely fulfilling the user's rights and avoiding potential legal issues. Options A and C represent incomplete deletions, while option D is a separate request process.
7 / 10
In a Slack channel discussing data deletion strategy, Mark from the Data Governance team sends the following message: 'I'm scheduling a bulk delete on the old customer support tickets. We need to ensure we're using a logical deletion approach – preventing accidental reintroduction of data via restores.' What is the primary benefit of implementing a logical deletion in this scenario?
A logical deletion – often achieved through flags like 'deleted_at' or soft deletes – prevents accidental restoration of deleted records. This contrasts with physical deletion (option C), which removes the data entirely and can disrupt backup/restore operations. Maintaining historical records for auditing is a key advantage, ensuring traceability without compromising data integrity.
8 / 10
Reviewing a PR to implement a new deletion pipeline for e-commerce product data, David, the Senior Developer, adds this comment: 'Before merging, we need to add a timestamp field to each deleted product record. This will be crucial for our technical audit trail – specifically, demonstrating that the deletion was performed and when.' What is David's primary concern regarding the technical audit trail?
David is focusing on creating a robust technical audit trail – which directly addresses potential issues with data consistency. Timestamping the deletion provides immutable evidence of when the record was removed and is essential for debugging and confirming compliance requirements. While performance optimization (option D) is important, it's not the immediate concern highlighted in this scenario.
9 / 10
During a standup meeting, Emily, a Data Engineer, explains her team's work on data deletion. 'We're implementing a retention policy that dictates how long customer transaction records are kept before being automatically deleted.' What is the core purpose of this retention policy?
A retention policy defines a specific timeframe for storing data before it's automatically deleted or anonymized. This directly addresses legal and regulatory requirements (option B), which often mandate minimum retention periods for compliance purposes. While options C & D are benefits of data management, the core function is defining *how long* data is kept.
10 / 10
After a user requests deletion of their account, Alex, a Data Privacy Analyst, generates a report detailing the action. The report states: 'All associated customer data has been removed from the CRM and marketing automation systems, confirmed via database queries.' What type of deletion approach is Alex describing?
Alex's report indicates the use of logical deletion, confirmed through database queries. Logical deletion uses flags or markers to indicate that a record has been removed without actually erasing the data itself. This approach is common for maintaining audit trails and facilitating potential restoration (if needed) while complying with data deletion requests.
What will I practice in "Data Deletion Pipelines Vocabulary"?
This is a Privacy Engineering exercise set. It walks through 10 scenario-based multiple-choice questions built around real usage of privacy engineering terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 10 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the privacy engineering vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Privacy Engineering exercises?
See the Privacy Engineering exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — privacy engineering vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.