Portfolio ↗

Quiz

2868 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.

All areas2868 Architecture Fundamentals91 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication102 Enterprise Architecture100 Legacy Modernization92 AI-Era Architecture96 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience92 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98
Difficulty Any beginner intermediate advanced

91 questions in Data Governance & Semantics.

  1. Sensitivity Labelling intermediate

    An insurer must classify data sensitivity across a growing estate. What makes classification work rather than becoming a stale register?

    2 min answer digitclassificationautomationenforcement
  2. Sensitivity Labelling advanced

    Your catalogue labels columns Public, Internal, Confidential and Restricted, and propagation takes the maximum label of all inputs. A team joins a Restricted table of health claims to an Internal table of postcodes and publishes weekly counts by postcode and condition. What does the label say, what should it say, and what goes wrong with the rule?

    2 min answer classificationpropagationaggregationk-anonymity
  3. Tokenisation & Masking advanced

    A communications platform must reduce the systems handling customer phone numbers and message content. Tokenisation or field-level encryption?

    1 min answer tokenisationencryptionscope-reductionpii
  4. Tokenisation & Masking advanced

    A digital bank must reduce the systems that handle raw account numbers. What does tokenisation achieve, and what does it not?

    2 min answer jupitertokenisationscope-reductionvault
  5. Tokenisation & Masking intermediate Multiple choice

    A marketplace must stop storing raw phone numbers in its analytical estate. Analysts still need to join orders to support tickets by the same customer, and the company must be able to delete an individual's data on request. Which approach fits?

    2 min answer tokenisationhashingerasurejoinability
  6. Tokenisation & Masking advanced

    A payments gateway of the kind Razorpay operates tokenises customer mobile numbers before they reach the analytical estate, using deterministic tokens so analysts can still join orders to support tickets. Nine months later a red team reconstructs the mapping for a large share of customers without ever touching the token vault. What did the design assume, and which decision made the attack possible?

    3 min answer tokenisationpseudonymisationre-identificationenumeration
  7. Tokenisation & Masking intermediate

    Customer phone numbers are replaced with vault-issued tokens at ingest, and the four services allowed to see raw values call the vault to detokenise on demand. The vault becomes slow rather than down - p99 goes from 8 ms to 4 seconds - for three hours during the evening peak. What happens across the estate, and what stops it?

    3 min answer tokenisationvaultavailability-couplingtimeouts