A company is running their webshop on Google Kubernetes Engine and wants to analyze customer transactions in BigQuery. You need to ensure that no credit card numbers are stored in BigQuery
What should you do?
A company is running their webshop on Google Kubernetes Engine and wants to analyze customer transactions in BigQuery. You need to ensure that no credit card numbers are stored in BigQuery
What should you do?
To ensure that no credit card numbers are stored in BigQuery, the best approach is to use the Cloud Data Loss Prevention (DLP) API. The Cloud DLP API is specifically designed to detect, inspect, and redact sensitive information such as credit card numbers before data is ingested into BigQuery. This proactive measure ensures that sensitive data is never stored in BigQuery in the first place, providing a secure and efficient solution to the problem.
B is correct answer here.
https://cloud.google.com/bigquery/docs/scan-with-dlp
B. Use the Cloud Data Loss Prevention API to redact related infoTypes before data is ingested into BigQuery.
D is impossible. I support B
B is correct answer here. .
B. https://cloud.google.com/bigquery/docs/scan-with-dlp
"B" A and C are reactive measures. D is not related to hiding sensitive information. B is the only pro-active/preventative measure specific to hiding sensitive information. https://cloud.google.com/bigquery/docs/scan-with-dlp
B is the correct answer
B - you want to use dlp for that
Ans : B
D is silly
Cloud Data Loss Prevention API allows to detect and redact or remove sensitive data before the comments or reviews are published. Cloud DLP will read information from BigQuery, Cloud Storage or Datastore and scan it for sensitive data.
B is correct
https://cloud.google.com/bigquery/docs/scan-with-dlp
How can it be D? i'll go for B, DLP is the tool to scan and find sensible data
B is correct. DLP
DLP is the service specifically for this task.
B is correct. got this in exam. Dump is valid. Few new came but easy ones.
DLP for sure.