Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Data Access Models”
Purpose-Based Access
Granting access for a stated and recorded purpose rather than by role alone, which is what several data protection regimes actually require.
Access Pattern Driven Modelling
Designing the data model from the queries the application must serve, rather than from an abstract normalised representation of the entities.
Data Product Interface
The stable surface a data product exposes — its schema, its access path, its documentation and its guarantees — as distinct from the pipeline behind it.
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.
Minimum Necessary Access
Restricting each user to the health information required for their specific role and, in the strong form, to the patients they are actually treating.
Subject Access Fulfilment
The operational path from a request to a complete, verified, delivered response within the statutory period, across systems that were never designed for it.
Airbnb's Service-Oriented Migration
Airbnb decomposed a large Rails monolith by first extracting a unified data-access layer, so that services were built on owned data rather than on shared database tables.
Compute Isolation Boundary
The line across which one domain's analytical workload cannot affect another's performance, cost attribution or access.
Egress Pricing
The asymmetric charging model in which data entering a cloud is free and data leaving is billed, shaping architecture more than compute pricing does.
In-Country Processing
Keeping data within a jurisdiction across every path it takes — including backups, logs, telemetry, support access and the disaster recovery region.
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.
Operator Independence
The requirement that no foreign entity can be compelled to access or disclose data, which goes beyond where the bytes are stored to who controls the operator.
SQL vs NoSQL
A choice driven by access patterns, consistency requirements and query flexibility — not by data volume, which is the reason usually given.
Storage Tiering
Moving data between access tiers as it cools, so rarely-read data is not paying hot-storage prices.
Trust Boundary Diagram
A diagram marking where data crosses between zones of differing trust, which is the structure a threat model is built on and the form security findings are best communicated in.
Capital One's Data Centre Exit
A major US bank closed all eight of its data centres and moved fully to public cloud, treating governance automation as the enabling technology rather than a constraint.
Change Data Capture
Publishing a stream of a database's row-level changes by reading its replication log, without modifying the application that owns it.
Cloud Pricing Models
The purchase options for cloud compute — on-demand, committed use, and spot — which differ by up to 90% for identical hardware.
Control Plane and Data Plane
The separation between the machinery that makes changes to a system and the machinery that serves its traffic.
Cross-Zone Data Transfer
Charges incurred when data moves between availability zones within a region — invisible on architecture diagrams and a recurring surprise on cloud bills.
Data Catalog
A searchable inventory of datasets with their schema, owner, meaning, freshness, quality and classification.
Data Contract
An explicit, versioned, enforced agreement between a data producer and its consumers about schema, semantics, quality and change policy.
Data Discovery
Automatically scanning stores to find where sensitive data actually resides, as distinct from where the documentation says it should.
Your organisation receives its first subject access request. Nobody knows where the person's data is. How do you respond within thirty days?
Start the clock formally and verify identity first Record the date received. Verify the requester's identity robustly — responding to an impostor is itself a di
A transformation project has grown to 600 models with chains twelve deep. A change at the base has an unknowable blast radius. What do you do?
Treat it as a software architecture problem, because it is one Six hundred models with twelve deep chains is a codebase with no module boundaries. The remedies
A CDO proposes moving to a data mesh because the central data team is a bottleneck with a nine-month backlog. How do you assess the proposal?
Agree with the diagnosis, examine the prescription The bottleneck is real and it is structural rather than a matter of capacity. A central team receives data fr
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
A business sponsor asks for a real-time data platform because "the competition has one". Reporting is currently a nightly batch that lands at 06:00 and nobody has complained. How do you handle this?
Do not answer the technology question "Real time platform" is a solution, and it has arrived without a problem attached. Answering it directly leads either to a
A new platform must serve a public partner API, three internal front-ends with different data needs, and high-volume service-to-service traffic. Choose the API styles and defend the choice.
Resist "pick one" These are three different problems with three different consumers. Standardising on one style optimises for architectural tidiness at the expe
A query that ran in 50ms for two years now takes 90 seconds. Nothing was deployed and the data volume grew normally. What happened?
The most likely cause: a plan flip The optimiser's choice is a function of estimated row counts. As the data grows or its distribution shifts, an estimate cross
A regulated client requires that no traffic between their data centre and your SaaS platform traverses the public internet. Design the connectivity and justify the cost.
Two distinct requirements hiding in one sentence Traffic must not traverse the public internet — a routing requirement. The client must be able to demonstrate i
A regulator asks whether customer data is encrypted. The team says yes, disks are encrypted. Is that a sufficient answer?
What disk encryption actually protects against Someone obtaining the physical medium or a raw storage snapshot. In a cloud context that means a provider employe
A vendor SaaS product embeds a model that scores customers, and its output drives an automated decision in your process. Your model governance framework covers models you build. What do you do?
The obligation does not transfer with the outsourcing You are accountable for the decision. That the scoring is performed by a vendor changes who operates the m
Anomalous access to a customer database is detected. Walk me through the first day, and say what determines whether you can answer the regulator.
The first hours Declare an incident and assign command. Named commander who does not debug, operations lead, communications lead, scribe. Security incidents add
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
Data Access Models
Role, attribute and purpose-based access over analytical data, and how they compose.
Data Platform Tenancy
Multiple domains on shared storage and compute, with separable access and cost.
Data Residency
Keeping data within a jurisdiction, including backups, logs and support access.
Data Subject Rights
Access, correction, portability and erasure across systems that never planned for them.
Healthcare Data Protection
PHI handling, minimum necessary access, and audit expectations in clinical systems.
CQRS
Separating the write model from the read models that serve queries.
Geo-Restriction & Sanctions
Blocking access by jurisdiction, and the accuracy and evasion problems that come with it.
SQL vs NoSQL
Decided by access patterns and query flexibility, not by data volume.
Transformation Frameworks
Declarative SQL transformation with tests, lineage and versioned models.
Branching Models
GitFlow, trunk and release branches as delivery constraints rather than Git preferences.
Change Data Capture
Turning a database's replication log into a stream, and its coupling risk.
Client Caching & Data Layer
Stale-while-revalidate, invalidation and optimistic updates on the client.
Cloud Pricing Models
On-demand, committed and spot, and the crossover arithmetic.
Communicating Threat Models
Making risk legible to people who will fund or accept it.
Compute Models
Instances, containers and functions, and what each is priced and shaped for.
Consistency Models
Linearizable, sequential, causal, eventual, and the session guarantees between them.
Data Architecture
General material on structuring, storing and governing data.
Data Catalog
Discovery, ownership and technical metadata, and why catalogues go stale.
Data Classification
Knowing which fields are regulated, because every control depends on it.
Data Contracts
Producers committing to schema, semantics and freshness, and breaking builds when they do not.