DATABRICKS-DEP Question 89

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose B0

  - Correct answer : B — Have the mask return `YEAR(date_of_birth)` cast back to the column's date type for everyone outside HR, generalizing the value to birth year only. A . Returning `NULL` suppresses the value entirely, which satisfies the privacy requirement but destroys the birth-year information the analytics team was explicitly granted access to. Suppression is too aggressive for this requirement. B . Reducing the date to its year component is generalization: it keeps exactly the granularity the analytics team is authorized to see for age-band studies while hiding the exact day and month, and HR still receives the untouched value through the mask's conditional logic. C . A cryptographic hash of the date produces an opaque fixed-length string that cannot be grouped into meaningful birth-year bands or cast back to a date, so it does not give the analytics team the age information they are supposed to have. D . Token-vault lookups are built for reversible pseudonymization of identifiers like account or card numbers, not for producing a coarser, still-analyzable version of a date; the analytics team would receive an opaque token instead of a usable birth-year signal.