DEA-C01 Question 500
Single answerYou are tasked with designing a data pipeline to process sensitive customer information stored in Amazon S3. The data must be anonymized to comply with privacy regulations before being shared with a third-party analytics team. The anonymization process must ensure that it is computationally infeasible to reverse the anonymized values. Which approach would best meet this requirement?
- A
Use AWS Glue to replace sensitive fields with random strings.
- B
Apply a hashing algorithm with a unique key salt to anonymize sensitive fields.
- C
Use Amazon Macie to automatically mask sensitive data and export anonymized results.
- D
Encrypt the data with AWS Key Management Service (KMS) and share the encrypted values with the analytics team.
Show answer and explanation
Correct answer: B
Explanation
Hashing with a key salt is a widely used method for anonymizing data while maintaining consistency and ensuring irreversibility. By salting the hash, you add an additional layer of security, making it computationally infeasible to reverse the anonymization. This approach meets the requirements of protecting sensitive customer information while making it usable for analytics.
- A. Incorrect.
Replacing sensitive fields with random strings does not ensure a consistent mapping for anonymized values and can lack the computational infeasibility required for true anonymization.
- B. Correct.
Hashing with a unique key salt ensures sensitive data is anonymized consistently and irreversibly, meeting the requirement of making it computationally infeasible to reverse the anonymization.
- C. Incorrect.
Amazon Macie is a service for discovering and classifying sensitive data but does not directly support masking or anonymizing data for external sharing.
- D. Incorrect.
Encrypting the data with AWS KMS secures the data but does not anonymize it, as the original data can still be decrypted using the appropriate key.