You store sensitive health records in BigQuery and must comply with legal requests to delete an individual's data. Which design allows efficient deletion on request?

BigQuery supports DELETE statements, making direct deletion of rows based on a unique identifier efficient and straightforward for compliance. This method ensures complete removal of the specified data. Using the Data Loss Prevention (DLP) API and Data Catalog helps identify sensitive data but doesn't provide a mechanism for efficient deletion of specific individual records. It's more for discovery and classification. Creating a view to exclude data only hides it, rather than deleting it. The data still exists in the underlying table, which doesn't meet deletion requirements. Overwriting the unique identifier with a salted SHA256 hash obfuscates the data but does not delete it. The original sensitive data remains in the table, which is not compliant with deletion requests.