The Rehearsal
Test your compliance and Data Vault knowledge. By the end, you will have answered them all once already.
This is a self-assessment. Write each answer the way you would explain it to a colleague or a client.
Technical lens — focuses on reasoning, not recitation. Can you explain how you’d implement it and why Data Vault handles it well?
Communication lens — evaluates clarity. Is the answer conversational and consultant-grade, not legalistic?
For each question: write your answer in the textarea, then submit to see the model answer. There are 4 hidden trap questions — they look identical to regular questions until you submit.
Before diving in, let’s check where things stand. This is calibration, not scoring.
the examiner pushes for reasoning, not recitation. He wants to see how you think through a problem, not what you memorized.
Harder questions. the examiner is testing the edges of your understanding — the places where two concepts collide or where a simple answer is the wrong answer.
All questions answered. Now let’s see what landed and what needs polish.
The trap scorecard above tracks itself automatically. After completing all questions, review which traps you spotted vs. missed. The reflex to build: “I’d want to think through the specifics...”
These are the lines worth rehearsing out loud. Say them, don’t just read them.
“GDPR was written for transactional systems where you find a row and delete it. Data Vault was built to never delete anything. Resolving that isn’t just a legal problem or a technical problem — it’s both at once. The solution is architectural: PII Satellite isolation, Artificial Hubs, tombstone records. You design for compliance upfront so you never have to break the vault to honor the law.”
“Data Vault’s design choices — insert-only loading, load timestamps, source tracking on every row — weren’t built for compliance. But they happen to be exactly what regulators ask for under GDPR, DORA, and the AI Act. That’s not coincidence — it’s the same underlying principle: if you can reconstruct what happened and prove where data came from, you can demonstrate compliance.”
“I’d want to think through the specifics before answering that definitively — my instinct is [X], but I’d verify [Y] before committing to it in a client conversation.”