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.
Create a BigQuery view with regular expressions matching credit card numbers to query and delete affected rows.
B.
Use the Cloud Data Loss Prevention API to redact related infoTypes before data is ingested into BigQuery.
C.
Leverage Security Command Center to scan for the assets of type Credit Card Number in BigQuery.
D.
Enable Cloud Identity-Aware Proxy to filter out credit card numbers before storing the logs in BigQuery.
"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
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.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
saurabh1805
Highly Voted 4 years, 6 months agosaurabh1805
4 years, 6 months agojhkkrishnan
Most Recent 9 months, 3 weeks agopixfw1
11 months, 1 week agomadcloud32
1 year, 1 month agocloud_monk
1 year, 1 month agomadcloud32
1 year, 2 months ago[Removed]
1 year, 5 months agojsiror
1 year, 8 months ago[Removed]
1 year, 10 months agopedrojorge
2 years, 3 months agojaykumarjkd99
2 years, 5 months agoAwesomeGCP
2 years, 7 months agogiovy_82
2 years, 8 months agosudarchary
3 years, 3 months agosudarchary
3 years, 3 months agoAzureDP900
2 years, 6 months agorr4444
3 years, 4 months ago[Removed]
4 years, 1 month ago