MENU
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?
Suggested Answer: B
Get Premium Professional Cloud Security Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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.
34 comments · newest first
NA
Nan
10 months ago
Totally agree with B! DLP is essential for this.
CE
Cecil
10 months ago
Wait, can you really prevent credit card data from being ingested?
RO
Rolf
10 months ago
B is definitely the way to go!
CA
Carlee
11 months ago
I think A could work too, but it's not foolproof.
WE
Wei
11 months ago
C seems a bit overkill for this situation.
TA
Tanesha
11 months ago
I don't think enabling Cloud Identity-Aware Proxy would help with this specific issue. It seems more focused on access control rather than data redaction.
AM
Amalia
11 months ago
I feel like Security Command Center is more about monitoring than actually preventing sensitive data from being stored. Is that right?
AS
Ashanti
11 months ago
I'm not entirely sure, but I think creating a BigQuery view with regex might not be enough to prevent credit card numbers from being stored in the first place.
FR
Frank
12 months ago
I remember we discussed using the Cloud Data Loss Prevention API in class. It seems like a solid choice for redacting sensitive information.
VI
Victor
12 months ago
Option D with Cloud Identity-Aware Proxy sounds promising to filter out the sensitive data before it reaches BigQuery. I'll make sure to understand how that service works.
RO
Robt
12 months ago
Option C with Security Command Center could be a good way to scan for and identify any credit card numbers, but I'm not sure if that fully solves the problem of preventing them from being stored in the first place.
IV
Ivory
1 year ago
The regular expression approach in option A seems a bit risky to me. I'd rather use a more robust data protection service like the one in option B.
YV
Yvonne
1 year ago
Hmm, I'm not too familiar with the Cloud Data Loss Prevention API. I'll need to read up on that option to understand how it can help redact sensitive data.
CE
Cecil
1 year ago
This looks like a straightforward data security question. I'll focus on the key requirements - no credit card numbers in BigQuery and using the right Google Cloud services.
WI
Wilda
1 year ago
Option C with Security Command Center is an interesting idea, but I doubt it's the most efficient solution here. B is clearly the winner.
AL
Alana
1 year ago
Haha, option D made me chuckle. Filtering out credit card numbers with Cloud Identity-Aware Proxy? Sounds like a roundabout way to do it.
PE
Penney
1 year ago
C) Leverage Security Command Center to scan for the assets of type Credit Card Number in BigQuery.
BU
Bulah
1 year ago
B) Use the Cloud Data Loss Prevention API to redact related infoTypes before data is ingested into BigQuery.
WI
Willard
1 year ago
A) Create a BigQuery view with regular expressions matching credit card numbers to query and delete affected rows.
LE
Lelia
1 year ago
I think option C is the most efficient way to handle this situation.
AL
Alesia
1 year ago
I'm not sure, I think option A could also work if implemented correctly.
NO
Novella
1 year ago
I like how option B takes care of the problem proactively. Manually scanning and deleting rows with regex feels like a lot of work.
VI
Virgie
1 year ago
It definitely saves time compared to manually creating and deleting rows with regex.
KI
King
1 year ago
I agree, using the Cloud Data Loss Prevention API to redact infoTypes before ingestion is a proactive approach.
CL
Clare
1 year ago
User 3: Yeah, it's definitely better than manually scanning and deleting rows with regex.
AN
Antonio
1 year ago
Option B sounds like the best solution to prevent storing credit card numbers in BigQuery.
TY
Ty
1 year ago
User 2: I agree, using the Cloud Data Loss Prevention API seems like a proactive approach.
SC
Scarlet
1 year ago
User 1: Option B sounds like the best solution to me.
CL
Clay
1 year ago
I agree with Jesusa, using the Cloud Data Loss Prevention API sounds like the most secure option.
JE
Jesusa
1 year ago
I think option B is the best choice.
DO
Dorthy
1 year ago
Option B seems like the way to go. Using the Cloud Data Loss Prevention API to redact sensitive info like credit card numbers before ingesting into BigQuery is a no-brainer.
ET
Ettie
1 year ago
User 3: I think it's important to prioritize data security, especially when dealing with customer transactions.
KA
Karina
1 year ago
User 2: Agreed, that's a secure way to handle sensitive data.
CR
Crista
1 year ago
User 1: Option B seems like the way to go. Using the Cloud Data Loss Prevention API to redact sensitive info like credit card numbers before ingesting into BigQuery is a no-brainer.