Enforce GDPR's Right to be Forgotten Across a Complex Architecture
This tests your design of a verifiable, async deletion workflow. A strong answer proposes a central index metastore, an orchestrated workflow (e.g., Step Functions) for deletion, and an auditing layer.
This tests your ability to design a verifiable, async deletion workflow across diverse data systems. A great answer outlines three parts: a central index metastore mapping user IDs to data locations (e.g., S3 URI + row), an orchestrated workflow (like AWS Step Functions) to manage deletion, approvals, and retries, and a final auditing step to prove compliance. The main red flag is proposing a simple 'find and delete' script, which ignores immutable data stores, error handling, and the need for an audit trail.
Read the original → aws.amazon.com
- #data governance
- #system design
- #gdpr
- #data architecture
- #aws
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.