Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
29 results for “Retention & Purge”
Deletion Verification
Proving that a deletion actually removed the data everywhere it existed, which is a harder problem than issuing the delete.
Data Retention Policy
A defined rule for how long each class of data is kept, where, and what happens at the end of it.
Log Retention Tiering
Storing log data at different resolutions, costs and access latencies according to how old it is and how likely it is to be queried.
Retention Cost
The storage bill for keeping a log replayable, which is set by retention multiplied by throughput multiplied by the replication factor.
Crypto-Shredding
Encrypting each subject's data with its own key and destroying that key to render the data permanently unreadable, achieving deletion without deleting.
Hot, Warm and Cold Data
Classifying data by how frequently and how urgently it is accessed, so each tier can be stored on media priced for that access pattern.
Idempotency Scope
The boundary within which an idempotency key is unique and meaningful — per account, per endpoint, or global — and the retention window it lives for.
Immutable Backup
A backup that cannot be modified or deleted for a defined retention period, even by an administrator — the control that makes backups survive ransomware and insider error.
Legal Hold
Suspending deletion for specific records because of anticipated litigation or investigation, which must override the retention schedule and be provable.
Log Compaction
A retention policy that keeps only the most recent value for each key rather than deleting by age, so the log becomes a durable snapshot of current state.
Point-in-Time Recovery
Restoring a database to any moment within a retention window by replaying transaction logs onto a base backup, rather than only to a snapshot boundary.
Reprocessing Window
How far back a pipeline can be replayed, set by the shortest retention anywhere along the path rather than by intent.
Right to Erasure
A data subject's right to have their personal data deleted, and an obligation that reaches every copy an architecture has created.
Telemetry Cost Management
Controlling observability spend through sampling, retention tiering and cardinality limits without losing diagnostic capability.
Telemetry Sampling
Keeping a subset of traces or events to bound observability cost, chosen so the ones that matter survive.
Your platform is built on an append-only event log with a lakehouse behind it. Legal asks how you will satisfy erasure requests within 30 days. What is your answer?
Establish the actual scope first Erasure applies to personal data held about the subject, and it has exceptions — data retained under a separate legal obligatio
A CDC pipeline feeding your warehouse falls three hours behind during a source system's batch job, and the source's transaction log retention is 24 hours. What is the risk and what do you change?
The immediate risk Lag consumes the retention window. At three hours behind against a 24 hour retention, you have 21 hours of margin. If the consumer stops enti
After a content purge, your origin receives 400× normal traffic and falls over. The CDN is working as configured. What is missing and how do you fix it?
What is happening A global CDN has hundreds of points of presence, each with an independent cache. A purge invalidates the object everywhere at once , so the ne
A GDPR erasure request arrives for a customer. Where does their data actually live, and what makes this expensive to retrofit?
Where the data lives Longer than people expect, and enumerating it is most of the work: Primary database · read replicas · caches · search indexes · analytical
Design the audit logging for a system handling financial transactions. What is logged, where does it go, and what makes it hold up?
What is logged Significant actions only , defined explicitly rather than logging everything — an audit trail nobody can search is not usable evidence: Authentic
For each of these, choose a queue or a stream and justify it — order fulfilment tasks, an audit trail, cache invalidation, and rebuilding a search index.
Order fulfilment tasks — queue Each task is consumed once by one worker and is then irrelevant. Nothing re reads it; no second consumer needs the same task. Wha
Retention & Purge
Deleting from an append-only estate, and proving the deletion happened.
Data Lifecycle & Retention
How long data is kept, where it ages to, and how it is actually deleted.
Records Retention & Legal Hold
Keeping what must be kept, deleting what must go, and freezing both on demand.
Artifact Management
Immutable versioned outputs, promotion between repositories, and retention policy.
Log Management
Aggregation, retention tiering, search and the cost of keeping everything.
Observability Cost
Telemetry bills, cardinality control and retention tiering.
Streaming Cost
Always-on compute, retention and cross-zone traffic as the three bills that surprise.