A data governance team needs to store email addresses in a way that allows analysts to join datasets by user identity without ever seeing the raw email values. Which anonymization or pseudonymization technique is MOST appropriate for this requirement?
Answer & explanation
Correct answer: D
WHY D is correct: Deterministic (consistent) hashing maps each unique email to the same hash value every time. This means analysts can JOIN two hashed datasets on the hash column to correlate activity across tables — without ever accessing the raw email. Because SHA-256 (or similar) is a one-way function, analysts cannot reverse the hash to recover the original value, satisfying the anonymization requirement.
WHY NOT A: Suppression removes the data entirely, which means there is no identifier left to join on. This would make correlation across datasets impossible, which contradicts the requirement.
WHY NOT B: Generalisation replaces specific values with broader categories (e.g., exact age → age range, full email → domain). While it reduces identifiability, joining on a domain like 'gmail.com' is not meaningful for identifying individual users across datasets.
WHY NOT C: Tokenization is a pseudonymization technique — it replaces PII with a token while retaining a reverse-mapping. Because re-identification is possible via the mapping table, it does not fully anonymize the data. Additionally, if the goal is solely to enable joins without re-identification risk, hashing is simpler and does not require a mapping store.
WHY NOT E: Partial masking (showing part of the email) still exposes PII and would not prevent a determined analyst from identifying users. It is also reversible for common email patterns and does not constitute anonymization.