PROFESSIONAL-MACHINE-LEARNING-ENGINEER · Question #216
You are analyzing customer data for a healthcare organization that is stored in Cloud Storage. The data contains personally identifiable information (PII). You need to perform data exploration and…
The correct answer is A. Use the Cloud Data Loss Prevention (DLP) API to de-identify the PII before performing data. To ensure the security and privacy of sensitive PII fields during data exploration and preprocessing of healthcare customer data in Cloud Storage, the Cloud Data Loss Prevention (DLP) API should be used to de-identify the PII.
Question
Options
- AUse the Cloud Data Loss Prevention (DLP) API to de-identify the PII before performing data
- BUse customer-managed encryption keys (CMEK) to encrypt the PII data at rest, and decrypt the
- CUse a VM inside a VPC Service Controls security perimeter to perform data exploration and
- DUse Google-managed encryption keys to encrypt the PII data at rest, and decrypt the PII data
How the community answered
(64 responses)- A73% (47)
- B3% (2)
- C16% (10)
- D8% (5)
Why each option
To ensure the security and privacy of sensitive PII fields during data exploration and preprocessing of healthcare customer data in Cloud Storage, the Cloud Data Loss Prevention (DLP) API should be used to de-identify the PII.
The Cloud Data Loss Prevention (DLP) API is specifically designed to detect, classify, and de-identify sensitive data like PII through techniques such as redaction, tokenization, or format-preserving encryption. De-identifying PII before data exploration and preprocessing directly ensures the privacy of sensitive fields while allowing analysis.
Customer-managed encryption keys (CMEK) protect data at rest but do not de-identify the sensitive information; once the data is decrypted for processing or exploration, the PII remains in its identifiable form, failing to meet the privacy requirement during active use.
VPC Service Controls establish a security perimeter to prevent data exfiltration, enhancing overall security, but they do not inherently de-identify PII; data within the perimeter, when accessed for exploration, would still contain raw sensitive information.
Google-managed encryption keys, like CMEK, protect data at rest but do not de-identify PII; when the data is accessed for exploration and preprocessing, the sensitive fields would still be in their original, identifiable state.
Concept tested: PII de-identification for data privacy
Source: https://cloud.google.com/dlp/docs/de-identify-sensitive-data
Topics
Community Discussion
No community discussion yet for this question.