Answer-first summary for fast verification
Answer: Use a unique identifier for each individual. Upon a deletion request, delete all rows from BigQuery with this identifier.
The correct answer is A: 'Use a unique identifier for each individual. Upon a deletion request, delete all rows from BigQuery with this identifier.' This is because the primary requirement is to delete the specific individual's health data upon their request. Using a unique identifier for each individual and deleting the corresponding rows from BigQuery ensures that all related data is removed completely, fulfilling the legislative requirement. While option B offers an approach involving the Data Loss Prevention (DLP) API, it adds unnecessary complexity and does not ensure complete deletion as effectively as option A. Options C and D involve techniques like views and data masking which do not fully comply with the deletion requirement.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
You are a cloud architect working for a sports association that caters to members aged 8 to 30. The association collects extensive health data on its members, including information on sustained injuries, which is stored in BigQuery. Current data protection legislation mandates that any personal health data must be deleted upon request by the individual. You need to design a solution that meets this requirement while ensuring that the process is efficient and compliant. What should you do?
A
Use a unique identifier for each individual. Upon a deletion request, delete all rows from BigQuery with this identifier.
B
When ingesting new data in BigQuery, run the data through the Data Loss Prevention (DLP) API to identify any personal information. As part of the DLP scan, save the result to Data Catalog. Upon a deletion request, query Data Catalog to find the column with personal information.
C
Create a BigQuery view over the table that contains all data. Upon a deletion request, exclude the rows that affect the subject's data from this view. Use this view instead of the source table for all analysis tasks.
D
Use a unique identifier for each individual. Upon a deletion request, overwrite the column with the unique identifier with a salted SHA256 of its value.