Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Records Retention & Legal Hold”
Legal Hold
Suspending deletion for specific records because of anticipated litigation or investigation, which must override the retention schedule and be provable.
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.
Architecture Decision Log
The ordered, immutable collection of a system's decision records, read as a history rather than as a specification.
Changelog Stream
A stream whose records are keyed updates, so replaying it from the beginning reconstructs a table — the same information in the other of its two forms.
Cognitive Load
The total amount a team must hold in its head to work effectively, and a real constraint on how many services or domains one team can own.
Computation-Only Collaboration
Two parties analysing their combined data without either receiving the other's records, by permitting only queries whose outputs are aggregate.
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.
Decision Context Capture
Recording the situation, constraints and forces that made a decision reasonable, so that later readers can judge whether it still applies.
Decision Narrative
Writing a decision record so that the reasoning survives the author, focusing on the forces and the rejected options rather than the conclusion.
Deletion Verification
Proving that a deletion actually removed the data everywhere it existed, which is a harder problem than issuing the delete.
Denormalisation
Deliberately duplicating data across records to make reads cheap, accepting the write-time cost of keeping copies in step.
Flow Logs
Records of accepted and rejected network connections, giving a queryable history of what actually talked to what.
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.
Key Skew
An uneven distribution of records across partitions, which caps throughput at the busiest partition regardless of how many exist.
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.
Log Schema Consistency
Enforcing the same field names, types and semantics for structured log records across every service, so cross-service queries are possible.
Metadata Harvesting
Populating a catalogue automatically from the systems that hold the data, because anything requiring manual entry will be incomplete within a quarter.
Obligation Mapping
Translating each legal or regulatory requirement into the specific design constraints it imposes, so that compliance becomes a set of testable properties rather than a document.
Offset Management
How a consumer records its position in a stream, and the decision that determines whether processing is at-least-once or at-most-once.
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.
Regulatory Constraint
A legal requirement that removes design options — and one that must be established early, because it is not negotiable and is expensive to retrofit.
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.
Steady-State Hypothesis
The measurable statement of normal behaviour that a chaos experiment predicts will hold while a fault is injected, without which the exercise is not a test.
Structured Logging
Emitting log entries as machine-parseable key-value records rather than as formatted prose.
Target Tracking Scaling
An autoscaling policy that adds or removes capacity to hold a chosen metric near a target value, like a thermostat, rather than reacting to threshold breaches.
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.
Transfer Mechanism
The specific legal instrument permitting personal data to leave a jurisdiction, which must exist per flow and which architecture must make identifiable.
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
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
A list endpoint returning 2 million records times out on deep pages and returns 500 for validation failures. Fix both properly.
The pagination problem OFFSET 100000 requires the database to scan and discard 100,000 rows before returning the page, so each page is slower than the last. Off
Choose storage for four workloads: a Postgres data directory, user-uploaded images, a shared build cache, and seven years of audit records.
Postgres data directory — block storage It needs low latency random reads and writes and a filesystem, and it attaches to one instance. That is precisely block
Product wants to add a recommendation feature using browsing history. Legal asks for a data protection impact assessment. What does architecture need to supply?
What the assessment actually needs from architecture Legal cannot assess a feature description. They need the data facts, which only the design supplies: A data
Six weeks before launch, legal confirms that customer data for one market must be processed and stored in-country. The architecture is single-region in another jurisdiction. What do you do?
Establish exactly what the requirement covers Before designing anything, get three things in writing from legal: which data is in scope — usually a defined cate
You join a team with no decision records. Significant choices are made in chat and nobody can explain why the system is shaped as it is. How do you introduce ADRs without it becoming process overhead?
Start by writing them yourself, retrospectively, for three decisions Pick three choices that are currently causing confusion — why this database, why this integ
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
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
Records Retention & Legal Hold
Keeping what must be kept, deleting what must go, and freezing both on demand.
Architecture Decision Records
One decision, its context, alternatives and consequences, kept immutable.
Data Lifecycle & Retention
How long data is kept, where it ages to, and how it is actually deleted.
Retention & Purge
Deleting from an append-only estate, and proving the deletion happened.
Writing Decision Records
Context, alternatives and consequences, written once and never edited.
Artifact Management
Immutable versioned outputs, promotion between repositories, and retention policy.
Auditability
Tamper-evident, attributed records that survive async boundaries.
Cross-Border Transfer
The legal mechanism that permits data to leave, and the architecture that respects it.
Lawful Basis & Purpose Limitation
Why you may hold the data, and why that forbids the second use somebody proposed.
Log Management
Aggregation, retention tiering, search and the cost of keeping everything.
Observability Cost
Telemetry bills, cardinality control and retention tiering.
Regulatory & Data Protection Architecture
General material on designing under legal and regulatory obligation.
Streaming Cost
Always-on compute, retention and cross-zone traffic as the three bills that surprise.
Technology Radar
Adopt, trial, assess and hold — with movement, dates and owners.