Home / DE Professional practice test / Ensuring Data Security and Compliance / Question

Databricks Data Engineer Professional · free practice question

A healthcare data team is preparing a dataset for statistical analysis. The dataset contains exact patient ages (e.g., 34, 67, 22). The compliance officer…

Exam-style question on Ensuring Data Security and Compliance from the free DE Professional practice test, with the answer and a full explanation below.

Updated November 16, 2026

Ensuring Data Security and Compliance Easy

A healthcare data team is preparing a dataset for statistical analysis. The dataset contains exact patient ages (e.g., 34, 67, 22). The compliance officer requires that the published dataset cannot be used to re-identify individual patients from their age alone, but the distributed age values must still be useful for demographic analysis. Which technique should the data engineer apply?

  1. AHashing — apply SHA-256 to each age value to produce a fixed-length token.
  2. BSuppression — remove the age column from the published dataset before release.
  3. CTokenization — swap each age for a random token and keep a reverse mapping.
  4. DGeneralisation — replace exact ages with ranges such as '20-29' or '30-39'.
Answer & explanation

Correct answer: D

WHY D: Generalisation replaces specific values with broader categories or ranges, reducing the granularity of the data so that individuals are not singled out while the aggregate/demographic signal is preserved. Replacing exact ages with 10-year buckets (e.g., 34 → '30-39') is the canonical application of generalisation and is widely used in k-anonymity implementations for healthcare and research data.

WHY NOT A: Hashing converts exact ages to opaque fixed-length strings. This hides the age, but no statistical distribution or trend can be derived from a set of SHA-256 digests, so demographic utility is lost.

WHY NOT B: Suppression removes the column. This satisfies the privacy requirement but eliminates demographic analysis utility, which contradicts the requirement.

WHY NOT C: Tokenization replaces the age with a random token while retaining a lookup table. The tokens carry no demographic meaning and are useless for statistical analysis, and the retained reverse mapping means the data is pseudonymized rather than anonymized.

Take the full DE Professional practice test free →

Would you pass today?

This question is one of 60 in the free, timed Databricks Data Engineer Professional practice test. Take it and get a section-by-section score.

Start the free test →